I've been having a problem with named for a while, so I just unmerged and emerged it again, but that didn't solve it. If I try to start it from init.d/named, it says it is already running, though it is not. If I start it directly, I get this error in the log file:
Jan 31 12:55:11 oberon named[29528]: starting BIND 9.2.2 Jan 31 12:55:11 oberon named[29528]: using 1 CPU Jan 31 12:55:11 oberon named[29530]: loading configuration from '/etc/bind/named.conf' Jan 31 12:55:11 oberon named[29530]: listening on IPv4 interface lo, 127.0.0.1#53 Jan 31 12:55:11 oberon named[29530]: none:0: open: /etc/bind/rndc.key: permission denied Jan 31 12:55:11 oberon named[29530]: couldn't add command channel 127.0.0.1#953: permission denied Jan 31 12:55:11 oberon named[29530]: couldn't open pid file '/var/run/named/named.pid': Permission denied Jan 31 12:55:11 oberon named[29530]: exiting (due to early fatal error) If I change the named.conf file so the pid file is in /tmp, then it starts. I have not done anything to set up named to run chrooted, and ps shows all named processes to be running as root. I've tried to trace through the init script, but can't find the implementation of the service_started function. If anyone has any ideas or suggestions, I'd appreciate them. -- Chris Bare [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
