Paul wrote:
> That module is sucking 80~99% CPU on 1.3.5.  Anyone else seen this?

I had your problem where a particular message would cause the Clam process 
to vacuum up all the CPU, and another where a "killer" message would cause 
the Clam service to hang, and both were solved by upgrading Clam to the 
current version. This was about a month ago.

Evan 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to