httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: [PATCH] Child processes signalling server abort
Date Sat, 02 May 1998 23:56:25 GMT
Yeah... The idea is that the spawning storm would happen "fast enough"
and the #exits are "low enough" that we prevent glitches but still
protect ourselves from the current behavior... I tried to be
conservative on which errors were fatal..

Dean Gaudet wrote:
> 
> Er I meant, if it's a repeating not immediately fatal error it still dies.
> 
> Dean
> 
> On Sat, 2 May 1998, Dean Gaudet wrote:
> 
> > Yeah, but it still seems kind of pointless.  If it's a fatal error and all
> > the children are exiting, apache will entre a spawning storm until it
> > reaches the required #exits.  If it's not a fatal error apache will still
> > die mysteriously at some point later...
> > 
> > Dean
> > 
> > On Sat, 2 May 1998, Jim Jagielski wrote:
> > 
> > > Dean Gaudet wrote:
> > > > 
> > > > 
> > > > So I argue for simplicity... unless you can come up with a neato scheme.

> > > > 
> > > 
> > > Well, we could use a static that tracks the number of times the
> > > status from waitpid() is APEXIT_FATALCHILD and if >X then do the
> > > aborting. We could even log each time we get that error even if
> > > we don't abort. Sort of like a glitch filter.
> > > 
> > > -- 
> > > ===========================================================================
> > >    Jim Jagielski   |||   jim@jaguNET.com   |||   http://www.jaguNET.com/
> > >             "That's no ordinary rabbit... that's the most foul,
> > >             cruel and bad-tempered rodent you ever laid eyes on"
> > > 
> > 
> > 
> 
> 


-- 
===========================================================================
   Jim Jagielski   |||   jim@jaguNET.com   |||   http://www.jaguNET.com/
            "That's no ordinary rabbit... that's the most foul,
            cruel and bad-tempered rodent you ever laid eyes on"

Mime
View raw message