On Tue, Jun 06, 2006 at 06:28:48AM -0700, Arias Hung wrote: > intensive memory hogging nature of the beast. At present > I'm using a recent spamassassin compiled from the svn version > 3.2.0-r386260. My spamassasin logs have absolutely no trace of the spam
Just curious, is there a reason you're running 3.2.0? It's completely not
meant for production use yet.
> Thanks for your reply. I actually limit my maxchildren to 4 due to the
> intensive memory hogging nature of the beast. At present
[...]
> that gets through, but my procmail logs of course record the spam going
> into my Inbox. That's why I'm hoping for a hint on even
> where to begin troubleshooting the leakage.
Since you limited spamd to 4 children, if say, 6 messages come in that need to
be scanned, 2 will be left sitting around waiting for a child to free up. If
it takes long enough that spamc or whatever calling spamc times out, the
message will (likely) continue through unprocessed.
--
Randomly Generated Tagline:
Marv Albert: He's really showing us what a man with a cannon
in his chest can do.
pgpVJ9YZg37zY.pgp
Description: PGP signature
