Micha, On Sat, 2004-01-10 at 14:04, Micha Silver wrote: > So we need the perl script, > clamdwatch, contributed by Mike running every minute as a cron job.
To be honest, I've only had clamd die ~3 times in almost a year of production use. I don't consider this acceptable, but the alternatives I've looked at start at $10k/year and move up from there. I'm assuming the development team will be able to resolve the problem shortly--especially if we can get more debugging info to them. You probably don't need to run the script every minute, that's just what I'm doing. The side benefit is that you should immediately know if anything ever goes awry with the virus database (since the script actually requests a RAWSCAN of itself and contains the EICAR pattern). > Is this a reasonable alternative to the clamdwatch script > running as a cron job? Good question. It sounds like some of the people having problems with clamd crashing aren't actually seeing the master process die. See the ml archives for more info. If this is the case, then I would think that running clamd under daemon tools wouldn't help them. Can someone verify this? Don't get me wrong. I like daemontools and run several other daemons under it's 'supervision' (mydns, freeradius, dnscache, etc). Cheers, Mike ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
