> [mailto:[EMAIL PROTECTED] nombre de Trog
> Enviado el: Martes, 25 de Mayo de 2004 11:19 a.m.
>
> On Tue, 2004-05-25 at 15:41, Samuel Benzaquen wrote:
> > > Upgrade to 0.71.
> > >
> > > It was most likely waiting for a scanning thread to finish,
> which it has
> > > to do before it can reload th
On Tue, 2004-05-25 at 15:41, Samuel Benzaquen wrote:
> > 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 ha
> -Mensaje original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] nombre de Trog
> Enviado el: Martes, 25 de Mayo de 2004 09:28 a.m.
> Para: [EMAIL PROTECTED]
> Asunto: Re: [Clamav-users] freshclam: NotifyClamd or not NotifyClamd
>
>
> On Tue, 2004-05-25
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 /
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 serv
