>xargs is still limited by max line length, so this needs to be done >with care. Perl can also be used in place of clamdscan to feed file >names to clamd (which must be run as root). The advantage of Perl is it >can iterate over an array and of course manage all the logging.
Also, depending on how much resource you have available, you can runa script to call the md5 checksum, verify it and if it has changed pass it thorugh to clamscan without using xargs at all. A simple find / |clamscan will scan every file in the filesystem, but will also chew through resource unnecessarily. So, depending on how often, how many changes, it may be well worth your while to set up a decent script that runs clamscan just after calculating your md5 sums and validating them against your known good db, and takes any file that reports "OK" from clamscan and adding its name and md5 sum to the DB. Realistically, unless your full system is going to be changing all the time, this process should take less and less time as your md5 DB covers more and more of the files _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
