> would I be better off calling clamscan to scan the entire disk, or call clamscan 10,000+ times with unknown files?
I suppose a better wuestion would be: How often do you want to scan these files? The reason this becomes important is that if you are going to be doing this overnight during server non-utilisation periods, then having a sequential scanner like clamscan scan each individual file one at a time in an ordered list will be fine. This will ensure that any resources used do not use up everything on the box and any unexpected use will still have resource available. If you want to do this during peak server useage, then having clamd manage the resources through its config files (i.e. number of child processes, memory out of memory protection, number of hreads etc etc) would probably be a better idea. You could also set the "nice" value of clamd/clamdscan and ensure that even during large file scans, each child process does not usurp valuable cpu cycles that affect your user experience. _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
