I: Problem w startup (disperatly)
Bill Larson
bind9 at comcast.net
Thu Feb 24 19:24:45 UTC 2005
On Feb 24, 2005, at 9:01 AM, Mauro wrote:
> I cann=92t start bind cause of the following:
>
> Feb 24 14:44:01 netservicea named[3344]: couldn't open pid file
> '/var/run/named': Operation not supported
>
> Feb 24 14:44:01 netservicea named[3344]: exiting (due to early fatal=20=
> error)
Just guessing, because you haven't given us much to work with.
Are you trying to start "named" in a chroot environment, using the "-t"=20=
option? I'm guessing this because of your "/usr/local/dns" prefix to=20
the "var" directory. This looks like what someone would name the base=20=
of the chroot environment.
If so, your PID file specification must be in relation to the root of=20
the chroot environment. So, rather than just "/var/run/named", it=20
would be "/usr/local/dns/var/run/named".
Also, the information from your log file isn't clear. Is the name of=20
your PID file "/var/run/named", or is this supposed to be the directory=20=
that the PID file will reside in? If it is the name of the file, then=20=
a directory named "/var/run/named" will prevent the PID file from being=20=
created. If you could give us the contents of your named.conf file,=20
this would help us understand what is occurring. Specifically, what do=20=
you have specified for the "pid-file" option?
Bill Larson=
More information about the bind-users
mailing list