Pavel Sanda <[EMAIL PROTECTED]> writes: > no, this belongs to spamassasin file. > we have > SPAMDOPTIONS="-d -c -m3 -H" > so we should change m3 to ... hmm m1?
This is the big question. I have no idea where to look to see how long the messages take to go through the whole chain. If I look for the spamd processes, I see: [EMAIL PROTECTED] ~]$ ps auxw|grep spamd root 3361 0.0 0.6 29640 1644 ? Ss Feb01 0:01 /usr/bin/spamd -d -c -m3 -H -r /var/run/spamassassin/spamd.pid root 19132 0.9 8.9 34012 22988 ? S 11:48 0:25 spamd child root 19175 0.7 8.2 32604 21132 ? S 11:48 0:20 spamd child root 19181 1.6 42.4 163516 108572 ? S 11:48 0:45 spamd child So there are 3 children, but one of them is 5 times larger than the others. After a restart, I get: [EMAIL PROTECTED] ~]$ ps auxw|grep spamd root 20662 0.5 9.8 29640 25244 ? Ss 12:35 0:00 /usr/bin/spamd -d -c -m3 -H -r /var/run/spamassassin/spamd.pid root 20670 0.9 10.3 30936 26380 ? S 12:35 0:01 spamd child root 20671 0.5 10.2 30696 26080 ? S 12:35 0:00 spamd child root 20672 0.2 10.1 30436 25840 ? S 12:35 0:00 spamd child Now the 3 spamd children have a reasonable rss (the column before ?). Let's wait a bit and see whether this increases again. JMarc
