I think I recall reading somewhere that the bug that you mention effects people using Bayes and/or huge auto-whitelists. Or perhaps the bayes/auto-whitelist bug gives similar symptoms. Or more than likely I've just gone crazy 8^)
My auto-whitelist is 15 domains and I am not using bayes. I currently have max processes set to 45. That is the maximum number of child processes I can spawn and not use any virtual memory. So perhaps I should try setting the number of processes to 35 or so? The puzzling part to me is the fact that I am only seeing this problem on 1 out of 2 identically configured machines. Thank you, Tom -----Original Message----- From: Martin Hepworth [mailto:[EMAIL PROTECTED] Sent: Friday, January 21, 2005 3:17 AM To: J Thomas Hancock Cc: users@spamassassin.apache.org Subject: Re: Performance Problems Tom Known issue with spamdspawning too many children on SA 3.0.x. You can 1)reduce the number of children with the -m parameter. Alot of people have this to soemthing like 10 by default. If you reduce it to 5 or even 2 it should sort the problem 2) patch the source.... http://bugzilla.spamassassin.org/show_bug.cgi?id=3983 3) wait for 3.10 which will have a fix for this. Most people find 1) is a good option, but alot have also done 2). -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300
