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 [EMAIL PROTECTED] _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
