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. > > > > You could make it run more frequently, but then you would have to deal > > with timestamp comparisons. > > 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. Bowie _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
