> -Original Message-
> From: Tomasz Kojm [mailto:[EMAIL PROTECTED]
> Sent: Sunday, January 11, 2004 12:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Clamav-users] pretty basic question - clamscan
> vs clamdscan
>
>
> On Sat, 10 Jan 2004 21:04:50 +0200
> Micha Silver <[EMAIL PROTECTED]
On Sat, 10 Jan 2004 21:04:50 +0200
Micha Silver <[EMAIL PROTECTED]> wrote:
> faster but clamd dies every so often. So we need the perl script,
Which version of clamd ?
Best regards,
Tomasz Kojm
--
oo. [EMAIL PROTECTED] www.ClamAV.net
(\/)\. http://w
On Saturday 10 January 2004 8:48 pm, Philipp Grosswiler wrote:
> > That depends on how broken it is.
>
> I guess that's the problem with this virus. It is so badly written.
>
> > If what you have is a damaged piece of viral code, does it really
> > matter which virus it was before it got damaged?
> That depends on how broken it is.
I guess that's the problem with this virus. It is so badly written.
> Beyond a certain amount of loss of the complete virus, there
> isn't enough left to know what it was supposed to be, and besides, if
what
> you've got isn't the complete Mimail virus, it s
At 11:04 AM 1/10/2004, Micha Silver wrote:
Tomasz Papszun wrote:
On Fri, 09 Jan 2004 at 12:07:16 -0800, [EMAIL PROTECTED] wrote:
please be attentive to attributions. I wrote none of the text in this
message, though it is attributed to me above.
$ clamscan Worm.Yaha.Y.msg
Worm.Yaha.Y.msg: OK
--
Micha,
On Sat, 2004-01-10 at 14:04, Micha Silver wrote:
> So we need the perl script,
> clamdwatch, contributed by Mike running every minute as a cron job.
To be honest, I've only had clamd die ~3 times in almost a year of
production use. I don't consider this acceptable, but the alternatives
I
Philipp Grosswiler wrote:
I found out that ClamAV does not always recognize the Mimail virus,
instead it is reported as "Seriously Broken Zip", which may be correct,
but doesn't really identify the virus itself...
How can this be avoided? I would like to get the virus name instead of
the informati
Tomasz Papszun wrote:
On Fri, 09 Jan 2004 at 12:07:16 -0800, [EMAIL PROTECTED] wrote:
$ clamscan Worm.Yaha.Y.msg
Worm.Yaha.Y.msg: OK
--- SCAN SUMMARY ---
Known viruses: 19802
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 0.08 Mb
I/O buffer size: 131072
On Saturday 10 January 2004 6:49 pm, Philipp Grosswiler wrote:
> I found out that ClamAV does not always recognize the Mimail virus,
> instead it is reported as "Seriously Broken Zip", which may be correct,
> but doesn't really identify the virus itself...
>
> How can this be avoided? I would like
I found out that ClamAV does not always recognize the Mimail virus,
instead it is reported as "Seriously Broken Zip", which may be correct,
but doesn't really identify the virus itself...
How can this be avoided? I would like to get the virus name instead of
the information of a broken ZIP?
Regar
Hasn't there been problems with the stability of clamd for a long time?
Are those problems solved now?
I use MailScanner and it sends batches of files to scan so the speed
difference is negligible and I don't have to worry about if clamd has
stopped. Anyway, I find that it takes more time for S
At 01:11 PM 1/9/2004, Tomasz Papszun wrote:
A gigantic difference (as shown in my previous message) is caused by
wasting much time for launching the program (clamscan) and loading a
database into memory (while clamd has it loaded _already_).
But when you scan many files at once, you execute clamsca
* Alikhani <[EMAIL PROTECTED]> [20040110 09:47]: wrote:
> Hi all
> I am new that use clamav on my server suse-smp.
> I install clamav.0-65 , when I use this command :
> /usr/local/sbin/clamav-milter -blo /var/run/clmilter.sock
> it saya
> You must select server type (loca
13 matches
Mail list logo
