RE: [cobalt-security] Anyone else get this error?

["Matt Brown" <matt@xxxxxxxxxxxxxxxxxx>]

> >"E.B. Dreger" wrote:
> >
> > > I recommend people run
> > >
> > >         dig @a.rootservers.net . ns > /etc/named/db.cache
> > >         kill -HUP `cat /var/run/named.pid`
> > >
> > > in a monthly cron job.
> >
> >Thanks for the great and simply-implemented suggestion...

Well getting back to the original thread....

>Dec 29 11:53:09 www named[512]: couldn't create pid file
>'/var/run/named.pid'

This error occurs as bind now runs as user named, after a previous cobalt
patch. If you stop named, remove the /var/run/named.pid and start bin as
root, the problem does not occur.

Running bind as root is a bad idea, hence why an update was issued. So the
question is, how does one get rid of the error msg when correctly running
bind as named, as per the update ?

Matt


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.434 / Virus Database: 243 - Release Date: 25/12/2002