Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Sep 2004 09:41:28 -0500
From:      kallender@completecomputing.com
To:        freebsd-questions@freebsd.org
Subject:   Bind 9.3.0 on FreeBSD 5.2.1
Message-ID:  <1095950488.4152e09842a7b@mail.completecomputing.com>

next in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1095950488.4152e09842a7b>