René Berber wrote the following on 11/26/2006 1:26 PM -0800: > Bill Landry wrote: > > > Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800: > >> Hello everybody, > >> > >> > >> i have set up clamscan to scan all of the server using cron daily > >> ( /usr/local/bin/clamscan -r -i --exclude-dir=/sys --no-summary / ) > >> > >> > >> the scan is taking too long conisdered to other virus scanners (about > >> 6 hours) > >> why does it taking so much? > >> and how can i shorten it while still scaning all files every night. > > If you're running clamd, why not use clamdscan instead of clamscan, it's > > much faster? > > No, it's not faster. > > If you run clamscan or clamdscan once on a large number of files (as shown > above) the execution speed is about the same. If you run them many > times, say > once per file, then what you said applies. Yes, I see that clamscan does the right thing and only loads the signature at the beginning of the scan, then they stay resident until all files have been scanned. I did find a way to make clamdscan work on all files by running a second instance of clamd pointed at a different clamd.conf file. But since the only speed difference is in the time it initially takes clamscan to load the signatures at the beginning of the scan, the speed difference is very minimal.
Bill _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
