For what it is worth, I have had this issue recently and before in a previous version (oh, maybe around 5 months ago). In both cases it was due to clamd sig versions outstripping the installed version of clam32. It looks like some upgrades of the sig files can cause an outdated clam32 to behave really badly / crash / not start. Reinstalling via wiki instructions "ClamAV for Windows" fixed all. Current version on http://w32.clamav.net/ is 0.91.
As far as I can tell, neither File::Scan::ClamAV->ping() or ->steamscan() appear to have a setable timout to play around and test with unfortunately. I note one mention on this thread of symptoms without clamd on, so might not help, but is one to watch the logs for. ASSP 1.3.3.1, Win2k, Perl 5.008004 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
