Ok, this seems to be a *lot* more stable from a memory standpoint:
spamd -m 3 --max-conn-per-child=3
But now I'm seeing this in my mail logs every few seconds:
Nov 3 15:46:58 mail spamd[18881]: server hit by SIGCHLD
Nov 3 15:46:58
on track? I *want* 3.01
to work bad...
Thanks so much.
Oban Lambie
Rick Macdougall wrote:
Oban Lambie wrote:
The good news was that 3.01 was really, really good at tagging spam
and I'd love to get back to it. The bad news was that no matter what
I did I could not stop the memory problems and the resulting lock-ups
with 3.0 AND 3.01. I've been reading
jplesset wrote:
Oban, I'm having a somewhat similar issue, though a different environment.
SpamAssassin 3.0.1, Solaris 9, and iPlanet Messaigng 5.2p2. I find that
when I started spamd,with no special flags, other than -d, I got a large
number of spamd processes running. This number increased
