This is an interesting approach, but let me explain a little more. I will be running md5sums for every file on a system. I will then compare that list of md5sums against a list of md5sums that are know to be virus free. The files that do not have valid md5sums in the database will then need to be scanned. In a lot of situations this list of files will be in the thousands. At this point would I be better off calling clamscan to scan the entire disk, or call clamscan 10,000+ times with unknown files? I hope I am making this clear. Thanks for all of your help.
mcd On 9/8/06, Barry Gill <[EMAIL PROTECTED]> wrote:
Or if you maintain a file with the filenames and paths that you want to scan, you can use cat to output each line of that file to clamscan in the same fashion. cat filename | xargs clamscan _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
-- ** *** ***** ******* *********** _______________________________________________ http://lurker.clamav.net/list/clamav-users.html