ClamAV when not run in daemon mode is very slow in comparison to other
virus scanners. If your server is getting pushed to it's limits, the
first sign will likely be their vir directories piling up as a result of
ClamAV not finishing within the specified time configured in Declude Virus.
Terry,
Maybe if you could clarify. You are running ClamAV in daemon mode, am
I correct?
My point was that as of several months ago, the non-daemon installation
was a processor hog and took a lot of time compared to F-Prot, the best
performing scanner. Things might have changed since then. I
mentioned yesterday.
John
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Matt
Sent: Tuesday, November 16, 2004
10:21 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.Virus]
ClamAV scan time
Terry,
Maybe if you could clarify. You are running ClamAV in daemon mode
Has anyone using ClamAV had problems with it taking longer than 60 seconds
to run? After installing it last week and working out a few problems, it
has done well. Today I noticed a number of *.vir folders left on the drive.
The VIR*.log showed that ClamAV was not completing in 60 seconds. This
I have noticed this problem with large files, usually TIFFs.
No solutions though...
-- Original Message --
From: John Carter [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Mon, 15 Nov 2004 16:44:35 -0600
Has anyone using ClamAV had problems with it
ClamAV when not run in daemon mode is very slow in comparison to other
virus scanners. If your server is getting pushed to it's limits, the
first sign will likely be their vir directories piling up as a result of
ClamAV not finishing within the specified time configured in Declude Virus.
I
or size. SO I left it to see if other changes helped -
# Close the connection if this limit is exceeded.
StreamMaxLength 3M
-Nick
From: John Carter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject:[Declude.Virus] ClamAV scan time
Date sent
