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

• In context of messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Ben Davenport: "FastCGI traps signals?"
• Previous message: Michael Smith: "fastcgi processes start but the web server doesn't"
• In reply to: Michael Smith: "fastcgi processes start but the web server doesn't"
• Next in thread: Stanley Gambarin: "Re: fastcgi processes start but the web server doesn't"

Message-Id: <v0300781aaed737191d28@[204.255.152.44]>
In-Reply-To: <32B127E4.372A3F46@cursci.co.uk>
Date: Fri, 13 Dec 1996 09:49:08 -0700
To: fastcgi-developers@openmarket.com
From: Ben Davenport <bpd@merc.com>
Subject: Re: fastcgi processes start but the web server doesn't

Yep -- there are some other associated problems as well.  For instance if
you KILLHUP the server (to make it re-read its config files), any
AppClasses will be started _again_.  The current AppClasses do not die.

-Ben

On 12/13/96, Michael Smith wrote:

> Interesting little problem just discovered for apache mod_fastcgi.  If
> the web server does not have permission to write to the log files, httpd
> processes don't start up; however fastcgi processes do.  This is with
> apache 1.2b1.
>
> Mike


--
Ben Davenport   <bpd@merc.com>
Experience varies directly with equipment ruined.

• Next message: Ben Davenport: "FastCGI traps signals?"
• Previous message: Michael Smith: "fastcgi processes start but the web server doesn't"
• In reply to: Michael Smith: "fastcgi processes start but the web server doesn't"
• Next in thread: Stanley Gambarin: "Re: fastcgi processes start but the web server doesn't"