Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 22959 - net-dns/bind/bind-9.2.2.ebuild chroot'ed init script can't locate pid
Summary: net-dns/bind/bind-9.2.2.ebuild chroot'ed init script can't locate pid
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Brandon Low (RETIRED)
: 23328 23483 23624 26907 (view as bug list)
Depends on:
Reported: 2003-06-16 15:25 UTC by Ian Neubert
Modified: 2003-08-19 03:46 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Ian Neubert 2003-06-16 15:25:26 UTC
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/, but the default named.conf is putting it in 

Reproducible: Didn't try
Steps to Reproduce:

Actual Results:  
/etc/init.d/named stop 

* Stopping named...                                                      [ !! ]
Comment 1 Brandon Low (RETIRED) gentoo-dev 2003-06-21 11:03:40 UTC
did you make sure all your config files were up to date?
Comment 2 Joe Eversole 2003-06-23 09:17:10 UTC
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/ 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 @@
        if [ $CHROOT -a -d $CHROOT ] ; then
-               PIDFILE="${CHROOT}/var/run/named/"
+               PIDFILE="${CHROOT}/var/run/"
-               PIDFILE="/var/run/named/"
+               PIDFILE="/var/run/"
Comment 3 Michael C. Ferguson 2003-06-24 12:32:49 UTC
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/', so we should either change the default named.conf or apply Joe's patch to solve the inconsistency.
Comment 4 Martin Holzer (RETIRED) gentoo-dev 2003-06-24 12:48:23 UTC
*** Bug 23328 has been marked as a duplicate of this bug. ***
Comment 5 Martin Holzer (RETIRED) gentoo-dev 2003-06-24 12:50:09 UTC
reemerge bind, make sure all configs are up2date
Comment 6 Martin Holzer (RETIRED) gentoo-dev 2003-06-25 14:44:12 UTC
*** Bug 23483 has been marked as a duplicate of this bug. ***
Comment 7 SpanKY gentoo-dev 2003-06-27 16:48:42 UTC
*** Bug 23624 has been marked as a duplicate of this bug. ***
Comment 8 Martin Holzer (RETIRED) gentoo-dev 2003-08-19 03:46:02 UTC
*** Bug 26907 has been marked as a duplicate of this bug. ***