Re: fastcgi processes start but the web server doesn't

cjs@iamerica.net ("cjs@iamerica.net")
Fri, 13 Dec 1996 14:23:31 -0600 (CST)

From: "cjs@iamerica.net" <cjs2895@ns1.zencom.com>
Message-Id: <199612132023.OAA06810@zencom.com>
Subject: Re: fastcgi processes start but the web server doesn't
To: gambarin@openmarket.com (Stanley Gambarin)
Date: Fri, 13 Dec 1996 14:23:31 -0600 (CST)
In-Reply-To: <199612131849.NAA15144@u4-138.openmarket.com> from "Stanley Gambarin" at Dec 13, 96 01:49:49 pm

> 	- another alternative is to check for parent pid of the 
> FastCGI process manager usign getppid().  If it is 1 (no parent), then 
> we can assume that httpd daemon is not running and die.

Short of modifying Apache, which may not be an option if the Apache
group disagrees with your changes, I like the one listed above. If
apache calls some sorta module shutdown procedure before terminations,
that would be a logical place too.

Christopher