From owner-freebsd-questions@FreeBSD.ORG Thu Mar 8 22:03:59 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED63D16A404 for ; Thu, 8 Mar 2007 22:03:59 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id A4A3713C4BF for ; Thu, 8 Mar 2007 22:03:49 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan@localhost [127.0.0.1]) by dan.emsphone.com (8.14.0/8.13.8) with ESMTP id l28M3gKO066067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 Mar 2007 16:03:43 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.0/8.14.0/Submit) id l28M3ga1066066; Thu, 8 Mar 2007 16:03:42 -0600 (CST) (envelope-from dan) Date: Thu, 8 Mar 2007 16:03:42 -0600 From: Dan Nelson To: Chuck Swiger Message-ID: <20070308220342.GR86959@dan.emsphone.com> References: <45F081A0.4090000@enabled.com> <8A6FA495-EB92-4059-A972-0599669225D1@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8A6FA495-EB92-4059-A972-0599669225D1@mac.com> X-OS: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.14 (2007-02-12) Cc: Noah , User Questions Subject: Re: Stopping named: rndc failed, trying killall: . X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2007 22:04:00 -0000 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