> > I attempted to push a 59M email through clamd via clamdscan
> > (all body, not attachment) and clamd has started chewing up
> > RAM and CPU.
Does the e-mail include encapsulated RFC822 messages? If so, there has
been a fix to that recently.
-Nigel
--
Nigel Horne. Arranger, Composer, Typeset
On Mon, 22 Mar 2004 15:54:18 -0500
Jesse Guardiani <[EMAIL PROTECTED]> wrote:
> Any ideas on how to avoid this in the future? I'm running with
> ScanArchive and ScanMail (because I want the binhex feature on).
The problem may be connected with already discussed and fixed
/dev/urandom issue. Pleas
softlimit set to low? It's a release candidate, not a recognized stable
code. Just a thought.
Jesse Guardiani [EMAIL PROTECTED] wrote:
> Howdy list,
>
> I just upgraded from ClamAV 0.60 to 0.70-rc on my 4.8-RELEASE
> machine. It seems to be working OK, but it's not standing up
> very well under s
Howdy list,
I just upgraded from ClamAV 0.60 to 0.70-rc on my 4.8-RELEASE
machine. It seems to be working OK, but it's not standing up
very well under stress tests.
I attempted to push a 59M email through clamd via clamdscan
(all body, not attachment) and clamd has started chewing up
RAM and CPU.
