Hello,
Upgraded to clamav 0.88.2 on Sunday. We use clamdwatch to monitor clamd. Ever
since the upgrade, clamdwatch reports that clamd has hung about 8 to 10 times
a day -- sometimes more. (Our supporting shell script then restarts clamd.)
We run clamdwatch once a minute.
How do we go about debugging this?
Any chance that clamdwatch is reporting a hung clamd when it is really not
hung? We
have verbose logging enabled and the last clamd log entry before shutdown is
almost
always the EICAR test sig.
Environment:
Solaris 9 w/ all security patches on a blade 250
load avg at time of reported hangs usually < 0.2
built with gcc version 3.4.1
clamav configure options (which have been in use for several years):
--enable-bigstack
--with-gnu-ld
clamdwatch is run with only the -q option
Thanks for all help!
Jon Kibler
--
Jon R. Kibler
Chief Technical Officer
Advanced Systems Engineering Technology, Inc.
Charleston, SC USA
(843) 849-8214
==================================================
Filtered by: TRUSTEM.COM's Email Filtering Service
http://www.trustem.com/
No Spam. No Viruses. Just Good Clean Email.
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
