httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <>
Subject Re: [SHOWSTOPPER] SIGHUP caused a fatal and silent crash
Date Tue, 04 Feb 1997 01:03:04 GMT
On Mon, 3 Feb 1997, sameer wrote:

> > I saw this at least as early as 1.2b2; I know there have been some changes
> > since, but I think none which would create this behavior, since the parent
> > is actually waiting for each of the children (if'd it'd forgotten, things
> > might be fine since it'd go on with the restart procedure (of course, it
> > probably couldn't bind the address, so it'd probably die outright)).
> 	I've seen intermittent problems where -HUP would cause 'can't
> bind to port' errors. It appears that -HUP isn't killing all of the
> child processes. 

That is a different story, and possibly a different problem.  In that
case, it looks like Apache is loosing track of one of its child processes. 
The way the code is now, if Apache knows about a child process it is darn
hard for the parent to go on without the child exiting.

> 	I will hopefully find some time to do some debugging on this.
> -- 
> Sameer Parekh					Voice:   510-986-8770
> President					FAX:     510-986-8777
> C2Net

View raw message