Bowie Bailey schrieb: > From: Odhiambo Washington [mailto:[EMAIL PROTECTED] > >>* Bowie Bailey <[EMAIL PROTECTED]> [20050503 18:38]: wrote: >> >>>From: henry j. mason [mailto:[EMAIL PROTECTED] >>> >>>> i need to know when freshclam fails silently. >>>> i know freshclam includes options to alert on errors, >>>> but i'd rather have some other process looking at it >>>> and making sure it's doing the right thing. has anyone >>>> tackled this problem? or is this just too obscure? >>> >>> [---snip---] >>> >>> >>>> any ideas? i'm thinking about cobbling together something >>>> in perl to run from a cron job. >>> >>>That would be my choice. I've never had a problem with freshclam, but >>>if I wanted to monitor it, I would probably write a perl script to run >>>once a day and notify me if there is no entry for the current day. >> >>Why don't people think about the KISS principle? >>freshclam can run in foreground, just like clamd and daemontools were >>written by DJB, no? >>I run clamd via daemontools, and I believe freshclam can also be run >>same way, so no re-invention of wheels. > > The original problem was that freshclam simply stopped working. Daemontools > would have done nothing since the process was still running. > > A perl script such as this could also watch for the "OUTDATED" messages to > remind you that you need to upgrade. > Use logwatch (<http://www.logwatch.org/>) Not only useful for freshclam; I found it to be an invaluable tool when one has to admin more than a handful servers. With properly maintained filters, it sends you mail if and only if something unusual is in your logfiles.
Thomas _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
