restarting bind

[Jim Reid]

>>>>> "Nate" == Nate Campi <nate at campin.net> writes:

    Nate> BIND 8 still reponds to signals to control it's behavior as
    Nate> well as socket commnunications. It's not until BIND 9 that
    Nate> the signals are ignored.

BIND9 does not ignore signals. Most signals sent to a BIND9 name
server will cause the process to terminate. SIGHUP is a special case
presumably to provide backwards compatibility with the flat-earthers
who equate SIGHUP with a reload of the server. BIND9 has another
exception when it comes to signals: SIGPIPE is used for internal
scheduling IIRC.