On Thursday 17 June 2004 00:00, Ralf Guenthner wrote:
> Ralf Guenthner schrieb:
> > Hi list
> >
> > I know the issue of spamd spawning too many processes and what can be
> > done about that has been discussed here before. But until today my
> > system never had that problem, I didn't even have to use the -m switch.
> >
> > But after a crash today I can't get spamd to limit the number of child
> > processes. The system chokes itself to death every time I try. It has
> > 1GB of memory, so you can imagine how many spamd procs it takes to crash
> > it...
> >
> > Using SA 2.60, qmail-scanner, spamd/spamc and the following script in
> > /service/spamd/run:
> >
> > #!/bin/bash
> > export LANG=de
> > exec /usr/local/bin/softlimit -m 60000000 /usr/bin/spamd -m1 -x -L -D -u
> > qmaild 2>&1
> >
> > As you can see I even added the -m switch but after a few minutes, the
> > number of processes runs rampant again.
> >
> > I tried to throw out some of those extra .cf-files, like Stearn's
> > blacklist, and that seems to help, but shouldn't the -m work anyway??
> >
> > Any ideas greatly appreciated
> >
> > Cheers
> > Ralf G.
>
> Nobody cared to reply. But here's what I've found out in the meantime in
> case someone else had or will have the same issue:
>
> Reducing the number of extra .cf files in /etc/mail/spamassassin
> prompted spamd to honor the limit set by the -m switch. Adding more or
> larger files seems to cause the behavior I described in my first
> posting. No idea, if that's by design or a bug. But it sucks <g>
>
> Ralf G.

Ralf: If you have the horsepower, just try it running
spamassassin instead of spamd/spamc.

I found lots of stuff started working when I did that, and i suspect
spamd is sort of buggy.

-- 
_____________________________________
John Andersen

Attachment: pgpE5TGXHjOij.pgp
Description: signature

Reply via email to