Larger files (above?/? what size?) take LONGER for clamdscan to run then for clamscan to run.
Example, freebsd 6.3, 4gb ram, xeon, 3gb HTT, 10K rpm scsi drives. clamdscan /usr/ports/distfiles/perl-5.8.8.tar.bz2 9.7M Jan 31 2006 perl-5.8.8.tar.bz2 takes 24 second to run clamdscan, 15 for clamscan. If we used a 3 second 'threshold' in clamdscan, it MIGHT force larger files to use clamscan (backup scanner): (so, that one would take 18 second, which is still shorter than 24) any better way? use some type of wrapper to look at size and 'fail' over to backup clamscan? 5m file , clamdscan 15 seconds, clamscan 16 seconds. -- Michael Scheidell, CTO Main: 561-999-5000, Office: 561-939-7259 > *| *SECNAP Network Security Corporation Winner 2008 Technosium hot company award. www.technosium.com/hotcompanies/ <http://www.technosium.com/hotcompanies/> _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
