http://bugzilla.spamassassin.org/show_bug.cgi?id=3376
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|spamassassin- |
|[EMAIL PROTECTED] |
AssignedTo|[EMAIL PROTECTED] |spamassassin-
| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2004-05-16 12:21 -------
I've run out of weekend to work on this and the problem was not in the area that
I thought it was. I'm reassigning this back to spamassassin-dev in case somebody
better able to handle it can pick it up.
What I found out about this: I reproduce it regularly when running spamd under
Cygwin. In that environment running tests that call start_spamd in SATest.pm
leave the child spamd processes lying around until I kill them using Task
Manager.
When there are enough of these zombie child processes, the system starts bogging
down and the errors of this bug report may be one of the symptoms.
When I try make test under Redhat 9.0 I see no zombie child processes. So I
don't know if I have reproduced the same bug that Jon is reporting here in MacOS
X. Jon, would you run make test and see if there are increasing numbers of child
processes running perl and spamd as the t/spam* tests run?
If there are not zombie processes being created in the test under MacOS X then
this is a different bug and I have no insight into it.
I suspect that the problem under Cygwin is that signals and processes work
differently in that environment. Is there anyone who is familiar with how the
child processes are handled in spamd who also has Cygwin? If not, I'll open a
separate bug for the Cygwin case and collaborate with whoever is familiar with
the spamd portion of this.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
