If I look at your patch at the end of the mail you would like
to exit the process once the handler has been run. I see the
following problems with that approach:
1. exit(0): This does exactly what you do not like: A
function deeper down
in the call stack terminates the process.
In my humble opinion it is much simpler (and cleaner) to fix this
problem in one place...Apache, rather than in each module that may
face this problem.
So from the part of the Perl script I see
only two approaches:
1. Guidelines for script programmers that clearly state that
you have
-Original Message-
From: Rüdiger Plüm [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 12, 2004 2:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Bug: Apache hangs if script invokes fork/waitpid
[..cut..]
I think 1. is the problem in our case. If you do a fork in
your perl script
Somehow I feel that this problem exists in other (it not all) mpms
besides worker. Havent tested it though. Anybody know
of an mpm where the forked child wont close the connection ?
-Roshan
-Original Message-
From: Jeff Trawick [mailto:[EMAIL PROTECTED]
Sent: Friday, October 08, 2004
The Problem:
---
I notice Apache 2(worker mpm) is not able to correctly handle
a fork/waitpid invoked by a script used with mod_perl.
Here is a simple cgi perl script to reproduce the problem (run under
mod_perl).
#!/opt/perl/bin/perl
print Content-Type: text/plain;
Rather than fix the TS issues in all the 3rd party libraries that can be
used
with PHP's and its extension its more pragmatic to sort out thread/filter
issues
in PHP core. Since similar arguments can be made for Apache core too.
The same issue has certainly not stopped Apache 2.0 itself from
what is the issue exactly ?
-Original Message-
From: Austin Gonyou [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 4:18 PM
To: [EMAIL PROTECTED]
Subject: 2.0.32 + PHP 4 CVS
There may be some issue with PHP Apache2 SAPI and the worker
MPM. Since
that's what I'm
