On Mon, 2002-05-27 at 13:38, Gregory Neil Shapiro wrote: > pjklist> Funny thing about that, I actually created a /var/run/named directory > pjklist> for just the purpose of running named in a 'sandbox', chowned the > pjklist> directory bind:bind, and because I forgot to set the pid file path in > pjklist> named.conf, I see that it seems to write named.pid (owned by > pjklist> bind:bind) into /var/run without a problem. > > For named, the initial creation isn't the problem, it's the reloads and > restarts: > > # ndc reload > Reload initiated. > # tail -2 /var/log/messages > May 27 12:36:35 horsey named[142]: couldn't create pid file '/var/run/named.pid' > May 27 12:36:35 horsey named[142]: Ready to answer queries.
named(8) starts up as root, but demotes itself and chroots to the sandbox immediately after reading the command line. I assume it creates the pid file as soon as it starts up, before it processes its arguments. Using ndc isn't a problem if you use the -c option to point it to the correct socket. Cheers, Mike Makonnen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
