Bill Watson wrote:
I have not nailed down all the criteria for failure yet, but on more than
one 5.1 machine I have found that named was stopped after playing around on
a vnc session.
I will of course gather more symptoms as I can, but on these production
machines breaking named causes the users to become quite cranky with me. I
must proceed with caution or wear protective gear.
Generally has anyone found that the named process stops without much
provocation?
Running "service named restart" is all it takes to restart the process. You
see FAILED and OK as the restarted statuses.
Thanks for your guidance,
Bill Watson
I've had similar problems with a couple of packages over the years, I
think named and squid were the main culprits, and users do get cranky.
An entry like so in root's crontab is a handy workaround:
*/5 * * * * [ -f /var/named/chroot/var/run/named/named.pid ] !!
/sbin/service named restart
Note: one line
Note, Each five minutes might not be your choice, but chances are that
by the time anyone notices it's fixed.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
