Ignore it, it's a stray bug ;)ok, longer version....named chroot's to it's own directory after changing to user named, unfortunatly, that makes /var/run >relative to the new root, so it gets all confused, however, it doesn't need to recreate this fileanyhow since reload doesn't change the pid in the first place -/
That's sooo kewl and good to hear.. This was one of those "it makes no sense what-so-ever" mysteries. I could see the pid number in the file matched the pid number named was running as, so it was even more confusing.
> Here's the only two changes performed:
> useradd -c "Named" -u 25 -s /bin/false -r -d /
> etc/named named 2>/dev/null || :
I assume the above is a typo "named" not Named?
You know.... actually it isn't, but I thought the same when I saw it as well.. I'm still not sure "why" the first reference to "Named" is in caps, but that's the way it was posted on the board and I also found the same reference in a security doc regarding named on http://www.openna.com. So I just followed suite.. (I'd still love to know why).
Thanks for the help you guys, that puts that one to bed! Cheers! Craig _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com