> > > I had the same problem with spamass-milter a while back. What you need > > > is a "watchdog" script, something like this... > > > > > > > We had a problem similar to this this week, however, the problem wasn't > > due to a dead/core'd process. clamdscan actually hung for one reason or > > another and clamd had to be shot down with a -9. This took place just > > after the upgrade to .80rc4 and I attributed it to (possibly) having a rc3 > > clamd running with a rc4 clamdscan. Perhaps I did not adequately shut > > down rc3 before the update. Either way, I assume that clamdscan shouldn't > > hang if clamd is dead. I noticed that mail was backed up because the > > amavis delivery agent (ADA?) hung when it relayed to amavisd. Eventually > > the problem was found to be clamdscan hanging and restarting clamd (after > > a -9) seemed to work. > > > > Is anyone else experiencing similar problems? > > The only known crashing issue with clamd is due to broken versions of > libz. Either run zlib-1.1.4 or a fixed version of 1.2.1 (which some > vendors have issued, see CAN-2004-0797)
[EMAIL PROTECTED] ewheeler]$ rpm -qa | grep zlib zlib1-devel-1.1.3-19.1mdk zlib1-1.1.3-19.1mdk According to http://www.mandrakesoft.com/security/advisories?name=MDKSA-2003:033 this is a patched 1.1.3 which we installed way back in Feb when the advisory came out. Should I hand-upgrade to 1.1.4 anyway? Does Clam static or dynamic link to libz? -- Eric Wheeler Vice President National Security Concepts, Inc. PO Box 3567 Tualatin, OR 97062 http://www.nsci.us/ Voice: (503) 293-7656 Fax: (503) 885-0770 _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
