Knotd when HUP-reloading tries to load the original symlink's destination, not the default file
If the config file is a symlink (e.g. when using a kubernetes configmap), knotd follows the symlink and records the symlinks destination. When reloading via HUP signal, it tries to read the original symlink destination, not the new one.
Example:
> cd /etc/knot
> mkdir orig
> mv knot.conf orig/
> ln -s orig/knot.conf .
> knotd -d # or watching knot with stderr logging in another window
> mv orig new
> ln -fs new/knot.conf .
At that point, knotd
will log that it can't find /etc/knot/orig/knot.conf
(which does not exist anymore).
I would strongly prefer following symlinks later.