On Mar 8, 2007, at 2:03 PM, Dan Nelson wrote:
[ ... ]
It would be nifty to make ndc/rndc smart enough to understand how to
find the pidfile under the chroot location.
rndc doesn't need to know where the pid is; it connects directly to
named over the control port (953) to do its magic. Try
HI there,
So I Have 6.2 install on my machine and restarting named gets the
following error.
any clues what is creating this?
# /etc/rc.d/named restart
Stopping named: rndc failed, trying killall: .
Starting named.
bind is starting just fine
Mar 8 13:34:47 named[52886]: starting BIND
On Mar 8, 2007, at 1:35 PM, Noah wrote:
So I Have 6.2 install on my machine and restarting named gets the
following error.
any clues what is creating this?
# /etc/rc.d/named restart
Stopping named: rndc failed, trying killall: .
By default, named runs in a chroot()ed environment under /var
In the last episode (Mar 08), Chuck Swiger said:
On Mar 8, 2007, at 1:35 PM, Noah wrote:
So I Have 6.2 install on my machine and restarting named gets the
following error.
any clues what is creating this?
# /etc/rc.d/named restart
Stopping named: rndc failed, trying killall
