Hello Bowie, > Since I have never seen the clamd daemon crash on any of my servers, I'm > not particularly interested in having a program waste resources checking > on it every 30 seconds.
It won't take up a lot of resources. It just periodically sends a signal to clamd. > Besides, why not use daemontools or one of the other existing process > monitoring programs? Why do we need a custom one for clam? Well the main reason is to allow the average user to just type: safe_clamd instead of: clamd and get the benefits of a monitoring script without any effort. Best regards -- Luca Gibelli (luca _at_ clamav.net) ClamAV, a GPL anti-virus toolkit [Tel] +39 0187 1851862 [Fax] +39 0187 1852252 [IM] nervous/jabber.linux.it PGP key id 5EFC5582 @ any key-server || http://www.clamav.net/gpg/luca.gpg _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
