Naik, Roshan wrote:
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 p
> 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 proces
Naik, Roshan wrote:
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.
I am not sure if it is really simpler (see below) but
admittedly it would make things easier for module authors.
So from
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 h
Naik, Roshan wrote:
-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
> -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
Naik, Roshan wrote:
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
[..cut..]
I think we have some kind of "works as designed" problem here. As far as
I un
Naik, Roshan wrote:
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 ?
BTW, does it makes any difference if you use a subproc api?
http://perl.apache.org/docs/2.0/api/A
8:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Bug: Apache hangs if script invokes fork/waitpid
On Thu, 07 Oct 2004 12:53:47 -0700, Paul Querna <[EMAIL PROTECTED]>
wrote:
> Jeff Trawick wrote:
> > I think there needs to be a mod_fork which provides a more general
> > purpose dae
On Thu, 07 Oct 2004 12:53:47 -0700, Paul Querna <[EMAIL PROTECTED]> wrote:
> Jeff Trawick wrote:
> > I think there needs to be a mod_fork which provides a more general
> > purpose daemon than that used by mod_cgid, and some Apache API will
> > know whether or not to send a request over there. This
Jeff Trawick wrote:
I think there needs to be a mod_fork which provides a more general
purpose daemon than that used by mod_cgid, and some Apache API will
know whether or not to send a request over there. This preserves the
goal of having fork() called only by single-threaded processes so that
all
On Wed, 6 Oct 2004 11:01:23 -0700, Naik, Roshan <[EMAIL PROTECTED]> wrote:
> 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.
>From Ulrich Drepper: "No threaded programs must use anything but _ex
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; charset=euc-jp\
13 matches
Mail list logo
