On Sun, Oct 19, 2003 at 12:21:52AM +0000, Daniel M. Drucker wrote: > > Yes, the situation I'm talking about is lots of spamd processes running at > > once using lots of memory. (Not to mention the local delivery processes > > running at the same time as well) > > > > Spamd using 800MB of ram is a bug, and one which I've never encountered > > yet in months of using spamd, so it's probably something to do with your > > particular config.....(perhaps a bug or corrupt installation of your > > version of Perl ?) > > I've encountered exactly this problem ever since upgrading to 2.60; > several times a day my system suddenly goes from having 1 or 2 spamds > to having 40 or 50 of them. It goes into swap, the load average goes > up to sixty or more, and the machine grinds to a halt. > > I've set up a perl script to kill all spamds and restart the spamd > service if it sees more than 10 instances, but that's a hack - I'd > rather just see the problem solved...
We've had a similar script running since 2.55 but it hasn't triggered since I constrainde the number of child processes allowed using the "-m" flag. About 50,000 emails a week, 2/3 spam, being processed by a dedicated spamd server having a 600 mHz processor and 384 megs RAM. Have you tried starting spamd with the "-m" flag to limit the number of copies? How much RAM are you using? -- Dan Wilder <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
