On Thu, 29 Sep 2005, A J Thew wrote:
> From: A J Thew <[EMAIL PROTECTED]>
> To: users@spamassassin.apache.org
> Date: Thu, 29 Sep 2005 11:33:42 +0100
> Subject: spamd dies with
>
> It appears that this (or similar) has been see by others but I'll
> give my 2p worth
> http://bugzilla.spamassassin.org/show_bug.cgi?id=4594
...
> at this point spamd stops responding complely until shutdiwn and
> re-started.
>
> I've reverted to --round-robin
It'll be cold comfort to you, but note that this doesn't affect
everyone. I've been happily using the Apache httpd server model
of "hot" child processes for spamd since Justin Mason produced the
patch for SpamAssassin-3.0.1. Currently running with that patch
applied to SpamAssassin-3.0.4 and I don't anticipate any problems
with SpamAssassin-3.1.0. Especially as I've got SpamAssassin-3.1.0
running on a dual-procesor OpenBSD box OK. My production machines
are single-processor OpenBSD boxes.
The last time I restarted spamd on the production boxes was 4th
July[1]. So they've been running happily for nearly three months.
The permanent spamds managing the child processes have all clocked
up 26 or 27 minutes of CPU time. Seems a bit pointless that I'm
runnning spamd under the control of daemontools to ensure it does
keep running.
[1] Yes this does mean I'm running with some slightly outdated rules
from the SpamAssassin Rules Emporium. The rules have been
updated, I just need to restart spamd to pick them up. Seems
such a shame when it's been performing so well :-)
--
Dennis Davis, BUCS, University of Bath, Bath, BA2 7AY, UK
[EMAIL PROTECTED] Phone: +44 1225 386101
