On Fri, 4 Feb 2000, Ounsted, Toby wrote:

>               I'm pretty sure it's the logrotate - the presumption being
> that named is trying to write to the file, the file gets rotated, named
> commits suicide.  The obvious one is to have named log to a file other than
> 'messages' and ot rotate that file but it's not a real fix and I don't think
> that named should behave that way in the first place..

How are you testing named's live/dead status? 

Specifically, what happens when you use nslookup to interrogate it after
the logs are rotated?

Does "ps aux | grep named" suggest that the process is still running?

I ask because I have named and logrotate coexisting happily.  However,
watching the log with "tail -f" had me puzzled once upon a time - until I
realized that named wasn't gone, it just wasn't logging where I was
looking.



-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to