named exits on SIGHUP?

[Joerg Pulz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 2 Jan 2005, Matthias Buelow wrote:

> Hi folks,
>
> when I kill -HUP named on 5.3 (BIND 9), it exits, instead of reloading, as 
> stated in the manpage.  Is this normal?  I think it's rather impractical, 
> since it prevents proper log rotation through newsyslog.conf (when using 
> "file" logging in named.conf).  It doesn't seem to matter if it's running 
> chrooted or not.

i noticed the same behavior.
it did not exit if named is running in foreground, started with "-f".

it's also impractical as '/etc/rc.d/named' is using the HUP signal for the 
reload command which causes the process to exit silently.
the named(8) manpage says in the SIGNAL section:
[snip]
In  routine  operation, signals should not be used to control the name-
server; rndc(8) should be used instead.
[snip]

i tried 'rndc reload' and it's working and did not cause the named process 
to exit. maybe '/etc/rc.d/named' should be changed to use this as reload 
command.

i have not looked deeper into this because my spare time is currently very 
limited.

regards
Joerg

- -- 
The beginning is the most important part of the work.
 				-Plato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFB2CenSPOsGF+KA+MRAuu2AJ9cS1wJIhYw3SyhqQyjVy5EP5e1YACglMWt
dMpKdIEqWEVjAB6CF7BoVbw=
=4lP4
-----END PGP SIGNATURE-----