On Tue, 06 Jun 2006, Theo Van Dinter delivered in simple text monotype:

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.

I usually try and use the latest bleeding edge on my client/workstation machine,
as i don't quite consider  it a 'production' machine, while familiarizing myself
with it in the process before upgrading 'production' level machines i 
administer.

Are you aware of any issues such as I described in 3.2.0?

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.
<---snip--->

Yes, I'm noticing copy_config timeouts ... could this be a consequence of too 
little
children?

Attachment: pgpchRYXXYQxl.pgp
Description: PGP signature

Reply via email to