http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313
------- Additional Comments From [EMAIL PROTECTED] 2007-02-27 23:59 -------
I too have having the same problem as the op. While I do not have a solution to
the referenced problem, I'm going to try hard coding
$self->{overloaded} to have a value of 0 in :
SpamdForkScaling.pm
For me, it seems this bug pops up when all 120 of my max children were at one
point concurrently processing data, but then possibly during the cleanup code is
when something gets snagged.
In other words, I see the bug hit *after* hitting concurrency and not during nor
before. Whether this has relavance to $self->{overloaded} above I not sure, nor
sure of it's implications, but going to try it. ;P
~Paul
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
