From owner-freebsd-questions@FreeBSD.ORG Thu Sep 23 14:42:53 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 1AE2516A4CE for ; Thu, 23 Sep 2004 14:42:53 +0000 (GMT) Received: from ccs.completecomputing.com (completecomputing.com [207.90.211.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E4F43D4C for ; Thu, 23 Sep 2004 14:42:52 +0000 (GMT) (envelope-from kallender@completecomputing.com) Received: from ccs.completecomputing.com (ccs.completecomputing.com [127.0.0.1])i8NEfSpd031091 for ; Thu, 23 Sep 2004 09:41:28 -0500 Received: (from webmstr@localhost) by ccs.completecomputing.com (8.12.8/8.12.8/Submit) id i8NEfS2J031084 for freebsd-questions@freebsd.org; Thu, 23 Sep 2004 09:41:28 -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 09:41:28 -0500 Message-ID: <1095950488.4152e09842a7b@mail.completecomputing.com> Date: Thu, 23 Sep 2004 09:41:28 -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: 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 14:42:53 -0000 Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named is not running. bsd# ps x | grep named 11342 ?? SLs 0:00.51 /usr/sbin/named -c /etc/namedb/named.conf 11596 p0 RL+ 0:00.00 grep named bsd# and bsd# ./named start [: /usr/sbin/named: unexpected operator Starting named. bsd# ps x | grep named 11603 ?? SLs 0:00.05 /usr/sbin/named -c /etc/namedb/named.conf 11605 p0 RL+ 0:00.00 grep named bsd# I had originally set up this system with the Linux compatibility layer enabled which also resulted in complaints about ELF processing. These errors occur with bind 9.3.0rc4 (source install) and with 9.2.3 (ports install). I'm very confused and have stepped through /etc/defaults/rc.conf /etc/rc.d/named trying to trace the error to no avail. Any assistance would be greatly appreciated. This is not running in a chroot. Kyle