I emerged the bind ebuild and ran the commands that it told me to run to setup a chroot'ed environment, but the init script did not have the correct location for the PID file on line 25 of /etc/init.d/named. It is looking for it in ${CHROOT}/var/run/named.pid, but the default named.conf is putting it in ${CHROOT}/var/run/named/named.pid. Reproducible: Didn't try Steps to Reproduce: Actual Results: /etc/init.d/named stop * Stopping named... [ !! ]
did you make sure all your config files were up to date?
I saw this bug in the process of searching before submitting the bug I'm about to enter... but, I verified the init script is incorrect. I did this by changing the init script to show the correct locations (/var/run/named/named.pid). I deleted /var/bind. I deleted /etc/bind. I unmerged bind. I deleted the distfile from /usr/portage/distfiles. I emerge bind. It said 1 config file needed updated. I ran etc-update. This is what I got: Showing differences between /etc/init.d/named and /etc/init.d/._cfg0000_named --- /etc/init.d/named 2003-06-23 11:04:56.000000000 -0500 +++ /etc/init.d/._cfg0000_named 2003-06-23 11:14:02.000000000 -0500 @@ -22,10 +22,10 @@ fi if [ $CHROOT -a -d $CHROOT ] ; then - PIDFILE="${CHROOT}/var/run/named/named.pid" + PIDFILE="${CHROOT}/var/run/named.pid" KEY="${CHROOT}/etc/bind/rndc.key" else - PIDFILE="/var/run/named/named.pid" + PIDFILE="/var/run/named.pid" KEY="/etc/bind/rndc.key" fi }
I also had this problem with the initscript and incorrect pidfile location. With the default /etc/bind/named.conf, the pidfile is being set as '/var/run/named/named.pid', so we should either change the default named.conf or apply Joe's patch to solve the inconsistency.
*** Bug 23328 has been marked as a duplicate of this bug. ***
reemerge bind, make sure all configs are up2date
*** Bug 23483 has been marked as a duplicate of this bug. ***
*** Bug 23624 has been marked as a duplicate of this bug. ***
*** Bug 26907 has been marked as a duplicate of this bug. ***
