Bug 178050 - net-dns/bind will not start in chroot after configured
Bug#: 178050 Product:  Gentoo/Alt Version: unspecified Platform: x86
OS/Version: FreeBSD Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: bsd@gentoo.org Reported By: admin@easyshellz.com
Component: FreeBSD
URL: 
Summary: net-dns/bind will not start in chroot after configured
Keywords:  
Status Whiteboard: 
Opened: 2007-05-11 13:08 0000
Description:   Opened: 2007-05-11 13:08 0000 
Cannot start named in chroot using the init script


Reproducible: Always

Steps to Reproduce:
1.emerge bind (tested 9.3.2-r5 and 9.4.1)
2.nano -w /etc/conf.d/named and uncomment CHROOT="/chroot/dns"
3.emerge --config =9.4.1
4.echo "alias rndc='rndc -k /chroot/dns/etc/bind/rndc.key'" >> /root/.bashrc
5.source /root/.bashrc
6./etc/init.d/named start

Actual Results:  
 * Starting chrooted named ...
named: chroot(): No such file or directory                                     
                                                                     [ !! ]
 * ERROR: named failed to start

Expected Results:  
named starts with correct parm's.
 /usr/sbin/named -u named -n 1 -t /chroot/dns

commenting out the 
CHROOT="/chroot/dns"
in /etc/conf.d/named allows named start normal without chroot.

------- Comment #1 From Dan Coats 2007-05-11 13:18:48 0000 ------- 
starting bind from commandline in chroot functions normal.
#/usr/sbin/named -u named -n 1 -t /chroot/dns

------- Comment #2 From Pierre Guinoiseau 2007-05-12 22:55:10 0000 ------- 
Created an attachment (id=119053) [details]
Patch to correct the start-stop-daemon line to be compatible with plain sh

It works fine for me on my g/fbsd :)

------- Comment #3 From Roy Marples (RETIRED) 2007-05-12 23:19:48 0000 ------- 
Fixed, thanks.

No revbump as voxus assures me there's a new version in a week.