From owner-freebsd-questions@FreeBSD.ORG Thu Sep 23 15:05:32 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A356316A4CE for ; Thu, 23 Sep 2004 15:05:32 +0000 (GMT) Received: from ccs.completecomputing.com (completecomputing.com [207.90.211.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48F7E43D54 for ; Thu, 23 Sep 2004 15:05:32 +0000 (GMT) (envelope-from kallender@completecomputing.com) Received: from ccs.completecomputing.com (ccs.completecomputing.com [127.0.0.1])i8NF48pd031972 for ; Thu, 23 Sep 2004 10:04:08 -0500 Received: (from webmstr@localhost) by ccs.completecomputing.com (8.12.8/8.12.8/Submit) id i8NF4823031970 for freebsd-questions@freebsd.org; Thu, 23 Sep 2004 10:04:08 -0500 X-Authentication-Warning: ccs.completecomputing.com: webmstr set sender to kallender@completecomputing.com using -f Received: from ns1.prismequine.com (ns1.prismequine.com [199.120.78.141]) by mail.completecomputing.com (IMP) with HTTP for ; Thu, 23 Sep 2004 10:04:08 -0500 Message-ID: <1095951848.4152e5e82a440@mail.completecomputing.com> Date: Thu, 23 Sep 2004 10:04:08 -0500 From: kallender@completecomputing.com To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 199.120.78.141 Subject: Re: Bind 9.3.0 on FreeBSD 5.2.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 15:05:32 -0000 I installed Bind 9.3.0 on the machine using the information on this page: http://ezine.daemonnews.org/200303/bind9.html to completely replace the binary that is in the base OS install. It looks like there's a problem with the location of some of the installed pieces (support tools) of Bind 9.3.0. I haven't tried the final release version as yet, nor have I tried a pkg_delete on the base package. I suppose I can do that and see what happens, but would prefer to really understand the new rc command structure - it's different than the 4.x format that I'm used to. Do you have any other ideas? Manually using rndc returns the status (regardless of which rndc binary I call - original or copy), but it's still not picking up the status correctly. That doesn't work either: bsd# /usr/local/sbin/rndc status /usr/local/sbin/rndc: Command not found. bsd# which rndc /usr/sbin/rndc bsd# cp /usr/sbin/rndc /usr/local/sbin/rndc bsd# ls -ld /usr/local/sbin/rndc -r-xr-xr-x 1 root wheel 210024 Sep 23 09:57 /usr/local/sbin/rndc bsd# /usr/local/sbin/rndc status number of zones: 4 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF server is up and running bsd# /etc/rc.d/named status named is not running. bsd# ps x | grep named 11603 ?? SLs 0:00.65 /usr/sbin/named -c /etc/namedb/named.conf 12860 p0 RL+ 0:00.00 grep named bsd# If I kill named, the startup script, which if called thus: /etc/rc.d/named start should start named, doesn't start it. Instead I get this: bsd# killall named bsd# /etc/rc.d/named status named is not running. bsd# /etc/rc.d/named start [: /usr/sbin/named: unexpected operator Starting named. bsd# I can then manually issue: named which starts it running, but the status still doesn't get picked up. Is it possible that installing the Linux compatibility layer on initial install changed something? FYI, named didn't want to start up after the base install either - that was before I made any changes to the named binaries. Thx. kallender@completecomputing.com writes: > This is potentially a stupid question, but is there a known issue > with the rc script which controls named under FreeBSD 5.2.1? I think you are looking for something which doesn't exist. The only script involved with "controlling" named (that I know of) is /etc/rc. What I think you want in /usr/local/sbin/rndc. root@>> /usr/local/sbin/rndc status number of zones: 8 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF server is up and running Robert Huff