On 2008-10-03 22:25, Charles Gregory wrote:
> CONCRETE SUGGESTION FOR CLAMAV DEVELOPERS (and anyone else with
> minimal script writing skills):
>
> CLAMWATCH service.
> Either as cron job, or constantly running monitor daemon.
> - Checks if clamd service is running (if enabled in startup files)
> - Tests clamdscan with simple clean file and ICAR test
> - Tests clamscan with simple clean file and ICAR test
> Failure of any of these conditions results in notification
> via e-mail to frequently monitored admin account.
>
> A "watchdog" would not only detect failed startup, but also any possible
> random failures, including errors I've seen in previous versions where the
> daemon continues to 'run', but returns an error code to clamdscan.
I use this:
http://www.mikecathey.com/code/clamdwatch/
did save me frequently when I was running mail with clamdscan on
a server having not enough memory (and while the 0.8* clamav releases
still used lots of memory).
--
Paul Bijnens, xplanation Technology Services Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens@xplanation.com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
(text/plain)