Hello, > ls -d bin/* | parallel clamscan > looks easy but logging may be difficult in this case too.
ls -d bin/* |parallel clamscan --no-sumary {} >yourlogfile.txt works fine. Anyway, this is time consuming and require a huge RAM. Because on a 8 thread CPU, 8 instance of clamscan will be run. So it will load 8 instance of signature databases into RAM. The best settings I use in my script is : ls -d bin/* |parallel clamdscan -m --no-summary {} >yourlogfile.txt As far as I know, it is faster than clamdscan -m bin/* -- Best regards, Arnaud Jacques SecuriteInfo.com Facebook : https://www.facebook.com/pages/SecuriteInfocom/132872523492286 Twitter : https://twitter.com/SecuriteInfoCom _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml