Bug 110847 – bind-9.3.2_beta1 /etc/init.d/named has problems stopping named when chrooted

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Kevin 2005-10-29 17:03:33 UTC]

Summary says it all.  I think this is a problem with the pidfile being in
/chroot/dns/var/run/named/named.pid rather than /var/run/named/named.pid

When bind is not chrooted (setting in /etc/conf.d/named changed), then this
start file works fine for starting and stopping named.

Reproducible: Always
Steps to Reproduce:
1. install bind-9.3.2_beta1
2. set it for chrooted operation as per /etc/conf.d/named
3. configure properly, start it with /etc/init.d/named start
4. try stopping it with /etc/init.d/named stop
5. Fails with [!!]

Actual Results:  
See steps to reproduce

Expected Results:  
[ok]

[Comment 1 Arnaud Launay 2005-10-30 02:35:55 UTC]

By the way, the file included in 9.3.1 doesn't work either if there is no
pid-file directive in named.conf... Which is wrong, as it could either be in
another included file, either let not specified in order to use the default one.
A backup case should be presented if PIDFILE is null.

[Comment 2 Daniel Westermann-Clark 2005-10-30 10:54:19 UTC]

I'm seeing the same problem (incorrect PIDFILE value) with net-dns/bind-9.3.1-r6
running in a chroot.

[Comment 3 Arnaud Launay 2005-10-30 11:35:51 UTC]

Bug #107724 has the correct version for the chroot one, this bug should probably
be marked as a dup of it.

[Comment 4 Jakub Moc (RETIRED) 2005-11-01 04:45:21 UTC]

(In reply to comment #3)
> Bug #107724 has the correct version for the chroot one, this bug should probably
> be marked as a dup of it.

Thanks.

*** This bug has been marked as a duplicate of 107724 ***