Hello all,
I am having a problem with the latest build crashing as a service (ClamD). I am using the latest Tools and W32 version from the site. Here is the exception: The application, C:\Program Files\clamAV\clamd.exe, generated an application error The error occurred on 02/28/2007 @ 18:41:29.619 The exception generated was c0000005 at address 78180312 (MSVCR80!memchr) Faulting application clamd.exe, version 0.0.0.0, faulting module msvcr80.dll, version 8.0.50727.762, fault address 0x00050312 This is happening about twice a day, and I am not sure why. I am using the clamdscan.exe called from an app to scan my inbound email. If there is any logging I can turn on to help diagnose the problem please let me know. More than happy to help out. I was also curious about how to detect the service had crashed. I tried to set the recovery settings for the service, but that does not work. The service actually starts Clamd.exe. So when Clamd.exe crashed the clamservice is still running. I can't use the built in recovery tools to detect that. Shouldn't the service wrapper detect if the underlying service has crashed and restart it, or at least shutdown so the SCM in windows can detect the service is dead. Right now I am calling clamdscan.exe and if that returns an error code of 2 then I try clamscan.exe. That seems to be OK, but not a good solution. I love the system, it works great. Jason Short, Ph.D. Emerald Technology, Inc. _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
