Date: Thu, 8 Mar 2007 16:03:42 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Chuck Swiger <cswiger@mac.com> Cc: Noah <admin2@enabled.com>, User Questions <freebsd-questions@freebsd.org> Subject: Re: Stopping named: rndc failed, trying killall: . Message-ID: <20070308220342.GR86959@dan.emsphone.com> In-Reply-To: <8A6FA495-EB92-4059-A972-0599669225D1@mac.com> References: <45F081A0.4090000@enabled.com> <8A6FA495-EB92-4059-A972-0599669225D1@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: . > > By default, named runs in a chroot()ed environment under /var/named, > and thus the path to the PID file which rndc expects to find under > /var/run/named.pid actually gets put under > /var/named/var/run/named.pid. > > 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 running "rndc status" while named is running; if you get an error message complaining about midding rndc.conf or rndc.key files, you may need to configure that before rndc will work. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070308220342.GR86959>