Re: [cobalt-users] Named PID File (can't create)

["Gerald Waugh" <gerald@xxxxxxxxx>]

<flash22@xxxxxxx>  wrote Friday, April 13, 2001 2:03 AM
> On Thu, 12 Apr 2001, Craig Napier wrote:
> > Hi Group,
> >
> > I recently followed suite like many others on this list and changed "named"
> > on our systems to run as user "named" vs. user "root". But we're seeing this
> > error in our logs when we make DNS changes in the GUI.
> >
> > Apr 11 23:25:19 blue named[27721]: couldn't create pid file
> > '/var/run/named.pid'
> >
> > -BUT- everything appears to be running okay and with no (apparent) problems.
>
> 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 file
> anyhow since reload doesn't change the pid in the first place -/
>
> gsh
Oops! I just had an occasion to reload named, AND
Apr 13 05:17:39 fsn1 named[30833]: reloading nameserver
Apr 13 05:17:39 fsn1 named[30833]: couldn't create pid file '/var/run/named.pid'
It does not seem as though 'reload' would cause an access to
/var/run.named.pid, BUT.
Gerald