On Sat, Jan 31, 2004 at 12:57:52PM -0500, Chris Bare wrote: > 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:
[ errors snipped ] You get errors like that if you aren't running as the named user. When starting from the command line, you need to add the '-u named' option. Can't give you much more, though. Have you tried: # /etc/init.d/named zap # /etc/init.d/named start Sometimes my named has crashed on me, and the PID file that the init.d subsystem uses thinks it's still alive. The zap argument tells this subsystem that named has been 'stopped' manually. Hope this helps, Brian -- Brian Richardson Sun Certified Java Programmer GnuPG Fingerprint 132E 867F 4E73 0607 A4AA 49A7 CB0D BCC9 DEC2 886C Public Key available at http://www.cubik.ca/ -- [EMAIL PROTECTED] mailing list
