I am very satisfied with the detection rate of ClamWall running under Mercury on my Server 2003 platform. Not only viruses, but using the SaneSecurity signatures, hundreds of Phishing messages and other scams also eliminated.
What is a matter of concerned is that, perhaps once a month or so, ClamD seems to get itself into trouble and fail. The only way that I become aware of it is by checking the ClamWall logs and finding the "ClamD not responding!" line. Sometimes it appears that ClamD is not running, but manually starting it by double-clicking on the executable in clamav\bin does the trick. Alternatively, sometimes ClamD appears as a hung process or application, and stopping it via the Task Manager is required.
Has anyone on the list had a similar experience? Any ideas on how to be alerted as soon as there is a failure?
<p>I am very satisfied with the detection rate of ClamWall running under Mercury on my Server 2003 platform. Not only viruses, but using the SaneSecurity signatures, hundreds of Phishing messages and other scams also eliminated.
</p><p>What is a matter of concerned is that, perhaps once a month or so, ClamD seems to get itself into trouble and fail. The only way that I become aware of it is by checking the ClamWall logs and finding the "ClamD not responding!" line. Sometimes it appears that ClamD is not running, but manually starting it by double-clicking on the executable in clamav\bin does the trick. Alternatively, sometimes ClamD appears as a hung process or application, and stopping it via the Task Manager is required.</p><p>&nbsp;</p><p>Has anyone on the list had a similar experience?&nbsp; Any ideas on how to be alerted as soon as there is a failure?</p><p>&nbsp;</p><p>&nbsp;</p>