As soon as I did that, clamav stopped recognizing the virus.
I had been running clamd, and the Q-S.pl script was using clamscan_binary=clamdscan successfully for several weeks.
This morning I changed the clamscan_binary to clamscan, and immediately the logs began filling with CLAMSCAN:Worm.SCO.A.
What could be the cause of clamdscan stopping to work? I'd like to go back to using the clamd daemon to save memory and processing time for each message. The difference is dramatic, as has been mentioned here several times.
TIA --Micha
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
