Red Hat Bugzilla – Bug 11630
NDC reload generates spurious error message
Last modified: 2008-05-01 11:37:55 EDT
ndc reload generates following confusing message:
couldnt create pid file '/var/run/named.pid'
Note: The existing pid is used as the new PID id is inserted. Many
people on your redhat-install-list are getting confused by this.
NDC restart works just fine. I assume that it is a user change over
This should be fixed in the current version.
Tut mir leid bero, but it shows up still in bind-8.2.2p5-15 on beta2.
Jun 26 16:00:39 rock named: couldn't create pid file '/var/run/named.pid'
Jun 26 16:00:39 rock named: Forwarding source address is [0.0.0.0].1026
firstname.lastname@example.org is my other account.
ndc reload still generates couldnt create 'pid file /var/run/named' in beta 3
*** Bug 12754 has been marked as a duplicate of this bug. ***
Tested on bind-8.2.2-P5-24 and it is fixed.
Sorry that was wrong ndc reload still exhibits error message / ndc restart works fine. Not a show stopper.
*** Bug 13081 has been marked as a duplicate of this bug. ***
Can be fixed by recompiling bind to point named.pid to /var/named (chroot jail) or set the caching-nameserver software to
added to the options statement in named.conf.
Not the exact syntax (dont have it before me but it works)
The current version fixes this by moving the pid file to /var/run/named. Not
exactly the standard location, but better than making /var/run world-writable...
This error has re-appeared in Bind 8.2.3.
It's gone for good in 9.x