Hi,
After upgrading from unbound 1.1.1 to unbound 1.2.1, the daemon does not hide into the background after start. Configuration file and startup scripts were not modified for a long time. System: CentOS 4.7. Does anybody have an idea what can cause such behaviour?
Best Regards,
Vlad
Hi Artamonov,
The only thing I can think of is that the behaviour for include files,
files included in the config file with include: , has been changed for
relative pathnames. This fixed a bug where after reload it would use
different file names. I suggest using absolute pathnames in the
include: directive.
You should then have two files with the same name in different
directories , now another one gets read, and that file has do-daemonize:
yesno differently.
This is a little complicated, but you could have bad luck.
Perhaps there is simpler explanation for this?
Best regards,
Wouter
Artamonov Vlad wrote:
Are you building from source rpm of the EL-5 version or from source? Did
unbound actually start listening on port 53, or is it hanging in some
startup phase? Perhaps a quick test using 'strace -v -f /etc/init.d/unbound start'
would shed some light on this?
Paul