After emerging net-dns/bind-9.2.2-r3 attempt of starting the deamon are twarted by a broken init script Reproducible: Always Steps to Reproduce: 1. emerge bind 2. edit /etc/bind/named.conf 3. /etc/init.d/named start Actual Results: the init script belived the deamon was already running, dispite the program not running and absense of /var/run/named/named.pid Expected Results: start the deamon and report OK `/etc/init.d/named zap` fixed the problem so it isn't a major bug.. ebuild problem?
updated info, zap resets the init script, the init script says its started OK.. however top shows it hasn't started at all and further attempts to use the init script fails, back to the drawing board. the entire thing is non-functional
upon attempting to run bind with `named -n 1 -c /etc/bind/named.conf -u named` it died without any error messages, i retried the same command but adding the -g arg, and this was the result: Mar 16 00:42:20.593 starting BIND 9.2.2-P1 -g -c /etc/bind/named.conf -n 1 -u named Mar 16 00:42:20.593 using 1 CPU Mar 16 00:42:20.596 loading configuration from '/etc/bind/named.conf' Mar 16 00:42:20.597 listening on IPv4 interface eth0, 192.168.0.2#53 Mar 16 00:42:20.598 listening on IPv4 interface lo, 127.0.0.1#53 Mar 16 00:42:20.601 command channel listening on 127.0.0.1#953 Mar 16 00:42:20.601 ignoring config file logging statement due to -g option Mar 16 00:42:20.601 couldn't open pid file '/var/run/named.pid': Permission denied Mar 16 00:42:20.601 exiting (due to early fatal error) as you can see bind is attempting to use /var/run/named.pid as the pid file instead of /var/run/named/named.pid for which it has permissions to read and write files. If i remember correctly assigning the pid file a location is a compile time option, i'll look over the sources and ebuild now.
fixed in 9.2.5 thanks, Aidan