Description of problem: I updated /etc/unbound.conf and assumed that '/etc/init.d/unbound reload' should read my changes into the currently running server. However it turns out that it exits silently and the server process exits with the following message in /var/log/messages: Mar 9 09:58:25 viktor unbound: [27476:0] notice: quit on signal, no cleanup and statistics, because installed libevent version is not threadsafe Version-Release number of selected component (if applicable): unbound-1.0.2-5.el5 How reproducible: always Steps to Reproduce: 1. install unbound 2. start it with /etc/init.d/unbound start 3. verify that the process runs 4. Run /etc/init.d/unbound reload Actual results: the unbound process exits with a message in syslog Expected results: reloaded configuration files and continued unbound operation Additional info:
This is due to upstream not providing a recent libevent, causing all signals to shut down unbound. IMHO the reasonable workaround is to make the reload() function in the init script an alias to restart(). This can probably be switched back when upstream releases it's next major version, with an updated libevent, but for EL4 and EL5 we're stuck with this.
I've put Noa's suggestion in unbound-1.4.16-2 for EL5 (unbound has no el4 branch)