> Not too long ago, there was a problem with running ClamAV and > ASSP on Windows. I use the latest [tBB] version from > http://hideout.ath.cx/ClamAV/. It seems that it still might be causing > ASSP to lockup. Is anyone else having this problem?
Not with 2.0; the code handling ClamAV was rewritten since we (I and Thomas) found some issues with the standard "pm" and since then, I had NO issues at all The problem is due to the fact that the "pm" doesn't implement a "wait loop" for send/receive, now... sometimes (e.g. while reloading signatures) clamd will accept connections and will also accept commands, but those will sit in a "queue" and will ONLY be served after the reload (or whatever other process) completes, this in turn means that if ASSP relies on the standard "pm" any scan request will successully connect to the clamd but then the scan itself will be kept "on hold" causing the calling thread/process to stay "on hold"; the solution, in ASSPv2 case was rewriting (thanks a LOT Thomas) the calls so that they now use a timeout and better handle such issues, I dunno if such a code was also implemented in v1, if not then that's what is causing the issue ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
