>> > ./clamscan/.libs/clamscan file.exe >> > Linux Wally 2.6.18-53.1.6.el5 #1 SMP Wed Jan 23 11:28:47 EST 2008 >> > x86_64 x86_64 x86_64 GNU/Linux >> > MD5(file.exe)= e7e7dc7981a4089cdcb42d32247dc6e0 >> > ClamAV 0.94/8284/Thu Sep 18 18:54:57 2008 >> > file.exe: OK >> > >> > ----------- SCAN SUMMARY ----------- >> > Known viruses: 428321 >> > Engine version: 0.94 >> > Scanned directories: 0 >> > Scanned files: 1 >> > Infected files: 0 >> > Data scanned: 0.00 MB >> > Time: 0.869 sec (0 m 0 s)
Suggestion: Change "file.exe: OK" to "file.exe: not scanned - exceeds max-filesize" Change "Scanned files: 1" to "Scanned files: 0" and add a new count to the summary "Not scanned: 1". That will show that clamscan is doing exactly what it has been told to do, while protecting the OP from i) forgetting that there is a max-filesize default (as it's been years since he last saw it) and ii) forgetting that files now need to be checked for size before checking them for threats (as ridiculously large files are now considered to be normal data). Moray. "To err is human. To purr, feline" http://members.aol.com/edgwddirk _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
