Chrooted named wont be stopped

[petrjanda]

Something very funny going on here. "/etc/init.d/named" starts the named daemon, but "/etc/init.d/named stop" fails to stop it. I KNOW named is running via ps -aux. While investigating, i found 2 ways to stop it.

First way:
killall named
/etc/init.d/named zap

Second way:
Edit /chroot/dns/etc/bind/named.conf, the line that says location of the pid file, change it from /var/run/named/named.conf to /chroot/dns/var/run/named/named.conf and then stop it normally. But before you start it again change to the original pid file location. It seems like the initscript seek the pid file in the REAL /var/run/named location instead of the chrooted one (/chroot/dns/var/run/named).

Has one got a REAL fix for this?
_________________
There is, a not-born, a not-become, a not-made, a not-compounded. If that unborn, not-become, not-made, not-compounded were not, there would be no escape from this here that is born, become, made and compounded. - Gautama Siddharta

[WladyX]

Just upgraded bind, same issue, resolved by:

[r1]

Hi,

2 ways to solve this,

1) put your chrooted path to your pid-file in named.conf

for example change
pid-file "/var/run/named/named.pid";

by
pid-file "/[YOUR_CHROOT_PATH]/named.pid";


2) change the init.d/named file with this

# as suggested in bug #107724
PIDFILE=$(\
egrep -v \
"^([[:cntrl:] ]+(#|//|/\*)|(#|//|/\*))" \
${CHROOT}/etc/bind/named.conf \
| egrep -o -m1 "pid\-file +\".+\" *;" \
| cut -d\" -f2
)

by

# as suggested in bug #107724
PIDFILE=${CHROOT}$(\
egrep -v \
"^([[:cntrl:] ]+(#|//|/\*)|(#|//|/\*))" \
${CHROOT}/etc/bind/named.conf \
| egrep -o -m1 "pid\-file +\".+\" *;" \
| cut -d\" -f2
)



r1.



diff for init.d/named

25c25
< PIDFILE=$(\
---
> PIDFILE=${CHROOT}$(\

[petrjanda]