On Wed, 27 Oct 2004, Joe Maimon wrote: > > The ClamAV authors could put a stop to this by making clamdscan and > > clamscan the same program and then acting differently depending on > > which name is run. This is similiar to how gzip and gunzip are
>An action could then be taken to >alert someone if clamd died (|sendmail [EMAIL PROTECTED]). When clamd >hangs on our system, mail is deferred until I realize mail has stopped and as you can imagine, that is a bad thing. I run a cron once an hour that runs freshclam and does some clamd checks. If clamd is not running or errors, an email is sent, any clamd processes are killed and a new clamd is started. It has worked well for me. _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
