How to gracefully shutdown bind10 noninteractively

[Shane Kerr]

All,

On Mon, 2011-12-05 at 22:13 -0800, JINMEI Tatuya / 神明達哉 wrote:
> At Tue, 6 Dec 2011 02:19:30 +0000,
> "Spain, Dr. Jeffry A." <spainj at countryday.net> wrote:
> 
> > Upstart automatically keeps track of the PID of the main bind10
> > process and sends SIGTERM to it following the console command 'stop
> > bind10'. After a configurable amount of time, default 5 seconds, it
> > sends SIGKILL if the process is still running. The command 'reload
> > bind10' sends SIGHUP. Does bind10 respond to this signal as well?
> 
> The BIND 10 process doesn't catch SIGHUP.  Moreover, it's unlikely
> that the concept of 'reload' is implemented in BIND 10 in its
> traditional sense.  BIND 10 will be expected to be more dynamic, and
> while you should be able to make configuration changes to running
> systems, it will be a more incremental and local change to the
> specific part of the entire system that is effected to the change,
> rather than the global "reload".

Note that at some point we'll probably support a more traditional
configuration-file based mode of operation for people that really need
it, but have not yet implemented it. Also this will miss some of the
flexibility of BIND 10, so hopefully we can encourage people to use the
"native" configuration mechanisms.

Cheers,

--
Shane