-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
G.W. Haywood schrieb:
> Hi there,
>
> On Tue, 19 Dec 2006 Walter B?rger wrote:
>
>> I tried clamav 0.90rc2 and the scantime of clamav minimized to 30-50
>> seconds.
>
> If I understand this, you have found that ClamAV 0.90rc2 is ten or twent
On Tue, 19 Dec 2006, G.W. Haywood wrote:
> Has anyone else observed such large improvements?
Yes. 0.8.x boggs down on some MIME types. The 0.9x RC's have been much
faster.
==
Chris Candreva -- [EMAIL PROTECTED] -- (914) 967-7816
WestNet I
On Tue, Dec 19, 2006 at 11:12:54AM +, G.W. Haywood wrote:
> > I tried clamav 0.90rc2 and the scantime of clamav minimized to 30-50
> > seconds.
[..]
> Has anyone else observed such large improvements?
Well, I can only observe the fact that clamav is about 10 times slower
than our commercial sc
Hi there,
On Tue, 19 Dec 2006 Walter B?rger wrote:
> I tried clamav 0.90rc2 and the scantime of clamav minimized to 30-50
> seconds.
If I understand this, you have found that ClamAV 0.90rc2 is ten or twenty
times faster than the previous version of ClamAV that you were using.
Please would you c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jean-paul natola schrieb:
>
>
>>>
>>> jean-paul natola wrote:
>>>
Hi everyone,
>>>
>>> Hello.
>>>
I'm having a bit of a problem with clamav on my server-
I'm getting about 3 to 4 of these per hour- and I dont know why its
happen
jean-paul natola wrote:
> I'm running;
> Freebsd 5.4 clamav 88.7 SA 3.1.7
>
> In the paniclog /var/log/exim/paniclog is where I 'm seeing these
entries
> I did check the 'messages' log and there are no entries-
>
> It seems that clamav is timing out when it is attempting to scan large
> mes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jean-paul natola wrote:
>>> > How do I enable timestamping ?
>>>
>>> In /etc/clamd.conf, around line 34 :
>>>
>>> # Log time with each message.
>>> # Default: no
>>> LogTime yes
>>>
>>
>> was not happy with that
>> Starting clamav_clamd.
>> ERROR: Par
> How do I enable timestamping ?
In /etc/clamd.conf, around line 34 :
# Log time with each message.
# Default: no
LogTime yes
was not happy with that
Starting clamav_clamd.
ERROR: Parse error at line 34: Option LogTime doesn't support arguments
(got 'yes').
ERROR: Can't open/parse the
> How do I enable timestamping ?
In /etc/clamd.conf, around line 34 :
# Log time with each message.
# Default: no
LogTime yes
was not happy with that
Starting clamav_clamd.
ERROR: Parse error at line 34: Option LogTime doesn't support arguments (got
'yes').
ERROR: Can't open/parse the con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jean-paul natola wrote:
> How do I enable timestamping ?
In /etc/clamd.conf, around line 34 :
# Log time with each message.
# Default: no
LogTime yes
> and again it happened with the same type of message
>
> /var/spool/exim/scan/1GvHgK-000AQG-Eo/
jean-paul natola wrote:
Saw your other message, you probably want to enable time stamping to
correlate
(with the exim log) what is going on.
How do I enable timestamping ?
and again it happened with the same type of message
/var/spool/exim/scan/1GvHgK-000AQG-Eo/1GvHgK-000AQG-Eo.eml:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jean-paul natola wrote:
> I'm running;
> Freebsd 5.4 clamav 88.7 SA 3.1.7
>
> In the paniclog /var/log/exim/paniclog is where I 'm seeing these entries
> I did check the 'messages' log and there are no entries-
>
> It seems that clamav is timing out
jean-paul natola wrote:
Hi everyone,
Hello.
I'm having a bit of a problem with clamav on my server-
I'm getting about 3 to 4 of these per hour- and I dont know why its
happening
"malware acl condition: clamd: unable to read from socket (Operation
timed out)"
and yes mail is still com
jean-paul natola wrote:
Hi everyone,
Hello.
I'm having a bit of a problem with clamav on my server-
I'm getting about 3 to 4 of these per hour- and I dont know why its
happening
"malware acl condition: clamd: unable to read from socket (Operation
timed out)"
and yes mail is still comin
Tomasz Kojm wrote:
On Thu, 14 Dec 2006 16:59:23 -0800
Dennis Peterson <[EMAIL PROTECTED]> wrote:
Right about here I keep wishing clamd and freshclam had a --show-conf
argument that showed what the current config file says, where it found
it, sans comments. Like postconf in the postfix product,
On Thu, 14 Dec 2006 16:59:23 -0800
Dennis Peterson <[EMAIL PROTECTED]> wrote:
> Right about here I keep wishing clamd and freshclam had a --show-conf
> argument that showed what the current config file says, where it found
> it, sans comments. Like postconf in the postfix product, I suppose. How
René Berber wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jean-paul natola wrote:
Hi everyone,
Hello.
I'm having a bit of a problem with clamav on my server-
I'm getting about 3 to 4 of these per hour- and I dont know why its
happening
"malware acl condition: clamd: unable to read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jean-paul natola wrote:
> Hi everyone,
Hello.
> I'm having a bit of a problem with clamav on my server-
> I'm getting about 3 to 4 of these per hour- and I dont know why its
> happening
>
> "malware acl condition: clamd: unable to read from socket
18 matches
Mail list logo
