On Mon, May 24, 2004 at 06:41:45PM -0400, Ross Kramer wrote: >I've tried that. My problem is, since I have an extremely large amount >of email passing through, and the sizes vary, spamd eats up the CPU. >I've even tried a max limit of 2, (which isn't very efficient for my >setup) and if a couple of messages come in that are really big, spamd >chews up the cpu. I need to be able to limit spamd based on the loadavg, >not on the number of child processes spawned. > >Even when I set the max limit to 10, if 4 or 5 messages come in that >are about 100k, spamd floors the cpu, and still spawns off the last 5 >children to accomidate any more mail coming in. Naturally this sends the >loadavg through the roof.
fortunately spam doesn't come in big messages, yet. So you could use "-s max_size" with spamc to 40k and keep most or all spam within the radar. // George -- George Georgalis, Architect and administrator, Linux services. IXOYE http://galis.org/george/ cell:646-331-2027 mailto:[EMAIL PROTECTED] Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631
