Date: Mon, 12 Mar 2007 10:17:17 -0700 From: Chuck Swiger <cswiger@mac.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: Noah <admin2@enabled.com>, User Questions <freebsd-questions@freebsd.org> Subject: Re: Stopping named: rndc failed, trying killall: . Message-ID: <7D5C55E5-C525-471C-B12A-C47970EB8AF2@mac.com> In-Reply-To: <20070308220342.GR86959@dan.emsphone.com> References: <45F081A0.4090000@enabled.com> <8A6FA495-EB92-4059-A972-0599669225D1@mac.com> <20070308220342.GR86959@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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. "rndc status" works fine for me, but I recall that trying to use it to kill/restart named always fails when named is configured with chroot().... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7D5C55E5-C525-471C-B12A-C47970EB8AF2>