From owner-freebsd-current@FreeBSD.ORG Sat Mar 3 00:26:29 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 032BB1065670 for ; Sat, 3 Mar 2012 00:26:29 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id C061A8FC0A for ; Sat, 3 Mar 2012 00:26:28 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1S3cnY-000Kqy-Sl; Fri, 02 Mar 2012 19:26:08 -0500 Date: Fri, 2 Mar 2012 19:26:08 -0500 From: Gary Palmer To: Rotate 13 Message-ID: <20120303002608.GB65949@in-addr.com> References: <20120302231645.GA65949@in-addr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: freebsd-current@freebsd.org Subject: Re: src.conf ignored; phantom named X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2012 00:26:29 -0000 On Fri, Mar 02, 2012 at 06:48:12PM -0500, Rotate 13 wrote: > > As for named running, if you do > > > > sh /etc/rc.d/named restart > > > > does it succeed? If so, the 'named_enable="no"' flag must be set wrong. > > "sh /etc/rc.d/named restart" gives exactly what you would expect > ("Cannot `restart` named. Set named_enable to YES..."). > > > Also check to make sure that its not named from ports or some other > > location (e.g. check fstat or lsof or something to make sure its actually > > /usr/sbin/named and not from some other location) > > "fstat | grep /named" returns nothing (!), likewise "fstat | grep > /sbin". fstat only shows the inode number of the file, e.g. fstat -p 1283 | egrep '(^USER|text)' USER CMD PID FD MOUNT INUM MODE SZ|DV R/W bind named 1283 text /usr 333873 -r-xr-xr-x 1659284 r % ls -i /usr/sbin/named 333873 /usr/sbin/named > However: > > # procstat -b `pgrep named` > PID COMM PATH > 63121 named /usr/sbin/named > 63090 named /usr/sbin/named > > (I also never used ports BIND.) > > I would really like to figure this out before I do the necessary work > to remove unwanted BIND from the system. Processes running without > apparent reason, indicates something else is wrong. > > Thanks for the help so far. I am continuing to poke the system, just > looking for the right tool to find out how this got started (also > grepping logs which show start but don't seem to show why). I don't recall seeing in your original message - after the installworld, did you reboot? Does "ps auxww | grep named" show that the process predates your installworld? (The 9th column should show when the process started, from memory) If the named rc.d file shows that the flag is set correctly to disable named I'm not sure what else would start it. I'm also curious as to why two instances of named appear to be running. On the face of it that would appear to be broken as only one could bind to port 53. You're not running jails or anything similar are you? Gary