Steve wrote:
$ ps auwx | grep clamscan | grep -v grep | wc -l 42
$ ps auwx | grep procmail | grep -v grep | wc -l 94
$ ps auwx | grep clamassassin | grep -v grep | wc -l 55
--
The first few lines from top say:
--
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
15451 usr 20 0 35944 33m 872 D 2.7 3.3 0:00.60 clamscan
216 root 15 -5 0 0 0 S 0.7 0.0 0:03.80 kswapd0
15116 usr 20 0 76136 15m 668 D 0.7 1.6 0:03.30 clamscan
15299 usr 20 0 2584 1224 840 R 0.7 0.1 0:04.36 top
15428 usr 20 0 61288 57m 872 D 0.7 5.7 0:01.38 clamscan
1 root 20 0 1648 196 172 S 0.0 0.0 0:00.64 init
2 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kthreadd
--
The procmail configuration I've adopted hasn't changed in years...
--
DEFAULT=$HOME/.maildir/
SHELL=/bin/sh
MAILDIR=$HOME/.maildir
:0fw
* < 1024000
| /usr/bin/clamassassin | /usr/bin/spamc -f
--
Might be bug in clamd/spamassassin. But it could also be you are
being mail-bombed (e.g. infinite depth of compressed-in-compressed
attachements).
I recommend to include some limit for number of clamd/spamassassin
instances. Don't know if procmail has such a capability, but it is
easy to control it with wrappers like amavisd-new or MailScanner...
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
