Bind 9.3.0 on FreeBSD 5.2.1

kallender at kallender at
Thu Sep 23 07:42:53 PDT 2004


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# ./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

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

I'm very confused and have stepped through


trying to trace the error to no avail.  Any assistance would be greatly

This is not running in a chroot.


More information about the freebsd-questions mailing list