spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kris Deugau <kdeu...@vianet.ca>
Subject Re: Burst of large messages sometimes causes spamd to lock up
Date Tue, 31 Jan 2012 15:35:44 GMT
RW wrote:
> On Mon, 30 Jan 2012 18:04:58 -0500
> Kris Deugau wrote:
>
>> 23:23:32 mfs2 spamd/main[26981]: prefork: child states: BI
>> 23:23:34 mfs2 spamd/main[26981]: prefork: child states: BI
>> 23:23:35 mfs2 spamd/main[26981]: prefork: child states: BI
>> 23:39:20 mfs2 spamd/main[26981]: prefork: child states: BB
>> 23:39:20 mfs2 spamd/main[26981]: prefork: child states: BBB
>> 23:39:20 mfs2 spamd/main[26981]: prefork: child states: BBBB
>> 23:39:20 mfs2 spamd/main[26981]: prefork: child states: BBBBB
>
>
> This doesn't look anything like the spamd options you
> quoted. Suspiciously 5 is the default for max-children, and it's
> consistent with the defaults for min-spare and max-spare too.

I should have added a "...." on the bottom of that list;  I didn't think 
it useful to show the full progression up to the defined max_children 
setting of 60 (which it usually reaches within a second or two).  spamd 
is behaving properly at that point and chewing through mail as fast as a 
child process can grab some CPU.

-kgd

Mime
View raw message