On 01/27/2010 10:22 PM, Tim Boyer wrote: > I've read many of the 'clamscan is running too slow!' messages on the net - > hopefully, this is something a bit different, at least. > > I'm running clamscan/clamd on eight RHEL5.4 Linux systems, and have been for > a few years. I use clamd for the mail servers; for the other servers where > someone might possibly download a file to their home directory, I just do a > clamscan daily. > > Yesterday, on two systems, it crawled to a stop - took more than eight hours > to check the few directories I have it look at. I tried to scan a small > directory this afternoon - more than 13 minutes: > > ----------- SCAN SUMMARY ----------- > Known viruses: 1248649 > Engine version: 0.95.3 > Scanned directories: 3 > Scanned files: 79 > Infected files: 0 > Data scanned: 228.85 MB > Data read: 82.43 MB (ratio 2.78:1) > Time: 794.250 sec (13 m 14 s) > > It's a dual P4 with 2Gb memory, so it's not the fastest thing around - but > this is really, really slow. > > I've tried different directories; time is comparable. The clamscan file > itself hasn't changed - I've pulled a backup. Can't see anything weird in > any logs. > > Suggestions appreciated... >
It might be due to a DB update, so first of all try this: - turn off 3rdparty databases, check how long the scan takes - if that didn't fix it, try using an older main+daily.cvd (the one from the 0.95.3 release for example), see how long it takes Once you found out which database is the problem, we can try to narrow down the problem from there. Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
