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