> > > 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
> >
On Tue, 2004-10-12 at 18:56, [EMAIL PROTECTED] wrote:
> On Tue, 12 Oct 2004, Scott Rothgaber wrote:
> > Doug Hardie wrote:
> >
> > > have encountered quite a few situations in the last month where clamav
> > > just stopped working properly and had to be manually restarted.
> >
> > I had the same
[EMAIL PROTECTED] wrote:
> For added reliability, can we have clamdscan call clamscan if clamd
> is toast and has timed out?
>
> -Eric
I would really like to see that as well. I would rather run clamdscan
than clamscan but I don't because of reliability concerns.
--TWH
___
On Oct 12, 2004, at 10:56, [EMAIL PROTECTED] wrote:
On Tue, 12 Oct 2004, Scott Rothgaber wrote:
Doug Hardie wrote:
have encountered quite a few situations in the last month where
clamav
just stopped working properly and had to be manually restarted.
I had the same problem with spamass-milter a whi
