I have configured bind-9.2.1-16 on RedHat 9.0 I started the named daemon by /etc/rc.d/ini.d/named start. When i do stop, the message given is stopping named... but still the process is seen in the list.
I have also encountered it in redhat specifically. I use kill -9 to stop it. and i prefer kill -HUP to restart it then the redhat style to start it.
In Bind 9,
# rndc reload ==> load the zonefiles again
# rndc exec ==> clear cache, restart named completely
The kill -HUP stuff is there solely to provide reverse compatiblity with bind 8, and is no longer the recommended way to do this.
The reason why the redhat initscript fails is that restart sends a SIGKILL to the running nameserver.
It does not check to see if the name server is actually running, and could use a stale PID cache file - this may, of course, result in a totally unrelated process.being killed.
Then it doesn't check if the old one has died completely first, before starting the new named. So that if the old named is still running, named will bomb with a fatal error, leaving you with no nameserver running.
srs
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
