Red Hat Bugzilla – Bug 679989
bind dies on USR1 signal (SIGUSR1)
Last modified: 2013-04-30 19:48:57 EDT
Description of problem:
Sending bind a USR1 or USR2 signal (to increase/decrease debug output) kills it instead
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run bind
2. killall -USR1 bind
bind should increase debug level by +1
This doesn't seem like a bug for me. Per named(8) manual page:
In routine operation, signals should not be used to control the nameserver; rndc should be used instead.
Force a reload of the server.
Shut down the server.
The result of sending any other signals to the server is undefined.
May I ask you where did you find SIGUSR1/SIGUSR2 signals should increase/decrease debug output? `rndc trace` should be used instead.
Shoot, I'm showing my age here. Older named versions used SIGUSR1/SIGUSR2 to do the rndc trace function.
Should the server die when receiving any other signal than the three defined? Seems like it should just ignore them instead.
So, yeah, not a bug in that it's not supposed to do a debug change, but maybe it should ignore the signal altogether instead of die.
(In reply to comment #2)
> Shoot, I'm showing my age here. Older named versions used SIGUSR1/SIGUSR2 to do
> the rndc trace function.
> Should the server die when receiving any other signal than the three defined?
> Seems like it should just ignore them instead.
Well, other signals use their default signal handlers. SIGUSR* default handler is to terminate the running process (check `man 7 signal`) so they do what is expected.
Closing as notabug.