On Tue, 2004-05-25 at 13:59, Samuel Benzaquen wrote: > Hi all, > > We've been running clamd / clamav-milter for some weeks without problems, > but this morning one of the clamd processes hanged up on freshclam's > notification. > > We have 8 RH7.3 Linux servers, running sendmail 8.12.11 + clamd / ClamAV > version 0.70, clamav-milter version 0.70j. > > 7 out of 8 servers continued working after notification, but one hanged up > and queued the clamav-milter processes. > > It this a NotifyClamd problem? > Should I disable it and wait for clamd's auto check?
Upgrade to 0.71. It was most likely waiting for a scanning thread to finish, which it has to do before it can reload the sig DB. If a scanning thread fails to finish, that indicates a bug in the scanner somewhere (which may have been fixed already). You should try and recover the file that is has a problem scanning. -trog
signature.asc
Description: This is a digitally signed message part
