http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5416
------- Additional Comments From [EMAIL PROTECTED] 2007-04-13 02:58 ------- FWIW/HTH: it's my theory that this is more likely to happen on slower machines, or spamd installations with lots of large custom rulesets (are custom rulesets loaded during the tests?), b/c from what I understand, the first spamc connection attempt from those test scripts *might* be accepted by the server in the very short period of time between the instant the last child forks and the instant the first forked child finishes reporting that it's idle (ready to accept). So what my patch was trying to do was give SpamdForkScaling.pm a way to know if it was still in "startup" phase, which would have overriden the trigger for "overloaded" mode. But I botched the implementation as you can tell from Justin's commentary... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
