Tomasz Papszun wrote:
On Fri, 09 Jan 2004 at 12:07:16 -0800, [EMAIL PROTECTED] wrote:
please be attentive to attributions. I wrote none of the text in this message, though it is attributed to me above.
I've been following this thread and I'm trying to get my head around the different options for running clamav with qmail-scanner-queue.pl:$ clamscan Worm.Yaha.Y.msg Worm.Yaha.Y.msg: OK
----------- SCAN SUMMARY ----------- Known viruses: 19802 Scanned directories: 0 Scanned files: 1 Infected files: 0 Data scanned: 0.08 Mb I/O buffer size: 131072 bytes Time: 0.718 sec (0 m 0 s)
$ clamdscan Worm.Yaha.Y.msg /tmp/Worm.Yaha.Y.msg: Worm.Yaha.Y FOUND
----------- SCAN SUMMARY ----------- Infected files: 1 Time: 0.026 sec (0 m 0 s)
As you can see, clamscan didn't find a virus in the mail message, but clamdscan did!
1- Call clamscan for each mail message: The surest method, but slow.
2- Call clamdscan, which needs to have the clamd daemon running: Much faster but clamd dies every so often. So we need the perl script, clamdwatch, contributed by Mike running every minute as a cron job.
Is this a correct summary of what's been discussed?
On the Clamav site, in the clamd_supervised doc page, there's an explanation and scripts for managing clamd with the service mechanism of daemontools. Is this a reasonable alternative to the clamdwatch script running as a cron job?
Thanks, --Micha
Paul Theodoropoulos http://www.anastrophe.com
------------------------------------------------------- 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
