[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RAQ3 Latest Security Patch update - Logcheck report
- Subject: Re: [cobalt-users] RAQ3 Latest Security Patch update - Logcheck report
- From: flash22@xxxxxxx
- Date: Fri Nov 16 15:01:28 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Thu, 15 Nov 2001, Render-Vue wrote:
> Nov 14 19:55:06 ns named[656]: couldn't create pid file '/var/run/named.pid'
>
> I hadn't noticed the '/var/run/named.pid' part before on removing sites...
> Is it something to do with the security update?
> Or just me not checking logs as carefully in the past?
> Anything to be concerned about?
Probably been there for a while, it's a stray glitch from running named as
'named' instead of 'root', the recent security patch probably made it
appear...
I'd be more concerned if you don't see it ;0
Won't hurt anything, it's just unhappy because it can't write it's pid
lock as a chrooted user, since cobalt runs daemon services under a
seperate daemon manager, it's doesn't really need it anyhow, and it gets
it right initially...(It's complicated, there is an earlier post about it
from long ago when it first showed up ;)
(Just be aware that using NDC from telnet may do strange things, managing
dns from the GUI will be fine)
gsh