httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@worldgate.com>
Subject Re: [PATCH] Child processes signalling server abort
Date Sat, 02 May 1998 20:40:00 GMT
On Sat, 2 May 1998, Jim Jagielski wrote:

> I'm sure that there will be comments:
> 
> Index: src/include/httpd.h
> ===================================================================
> RCS file: /export/home/cvs/apache-1.3/src/include/httpd.h,v
> retrieving revision 1.206
> diff -u -r1.206 httpd.h
> --- httpd.h	1998/04/19 20:10:45	1.206
> +++ httpd.h	1998/05/02 20:17:55
> @@ -301,6 +301,27 @@
>  #endif
>  
>  /*
> + * Special Apache error codes. These are basically used
> + *  in http_main.c so we can keep track of various errors.
> + *
> + *   APEXIT_OK:
> + *     A normal exit
> + *   APEXIT_INIT:
> + *     A fatal error arising during the server's init sequence
> + *   APEXIT_CHILDINIT:
> + *     The child died during it's init sequence
> + *   APEXIT_CHILDFATAL:
> + *     A fatal error, resulting in the whole server aborting.
> + *     If a child exits with this error, the parent process
> + *     considers this a server-wide fatal error and aborts.

Would it be a good thing to wait until we have a few child processes
exiting with childfatal over a certain period before the parent exits?
It may be possible that some freak error could cause one normally
fatal error.  We don't want the whole thing to exit too quickly.

Do we want to call it APEXIT or AP_EXIT?

It would be cool if a child could use an exit status to cause a 
HUP or USR1, but that can be added later.


Mime
View raw message