Robert
theres a patch (well two actually) that help for 3.01 and 3.02 here
http://bugzilla.spamassassin.org/show_bug.cgi?id=3983
does alot of what the 3.10 will do - limits spawning of new processes.
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
[EMAIL PROTE
Thanks for the response. Yes it is:
--max-conn-per-child=number
I set it to 20. Will see how it works. Default is 200. Thanks again for
the help. I will look into the upgrade to 3.0.2.
Thanks again!
Robert
> -m10 is 10 max children. In 3.x each child gets reused more than once
> before it is t
-m10 is 10 max children. In 3.x each child gets reused more than once
before it is thrown away to reduce overhead of startup/shutdown. However,
this has the drawback that if a child sucks up a lot of memory doing one
spam, it has that memory until it goes away. By default that is a pretty
long t
Are you referring to whats in the spamd line? Currently it is m10
Hmm I thought that was max con per child, so where do I edit that value?
Thanks
Robert
> 3.0.2 is better than 3.0.1 in this regard, so the first thing I'd do is
> upgrade.
>
> That may not be a complete solution, so if you are usi
3.0.2 is better than 3.0.1 in this regard, so the first thing I'd do is
upgrade.
That may not be a complete solution, so if you are using spamd, I'd
set ---max_con_per_child to something reasonably low, like 20..50 or so.
There are still a couple of things that can eat memory and already have bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> Are there any memory problems for SA version 3.0.1? We recently upgraded
> to 2 gigs of memory on the server and SA just gobbled up the memory. We
> dip down to under 20 megs here and there and 30-40 megs the rest of the
>
