Jeff Trawick wrote:
On Sat, 20 Nov 2004 12:11:34 -0500, Jeff Trawick [EMAIL PROTECTED] wrote:
The ScriptSock directive must be used when there are two instances of
the server with same ServerRoot. If it is omitted, symptoms may
include
. wrong credentials for CGIs
. CGIs stop working for one
On Tue, 23 Nov 2004 12:18:11 -0500, Bill Stoddard [EMAIL PROTECTED] wrote:
Jeff Trawick wrote:
On Sat, 20 Nov 2004 12:11:34 -0500, Jeff Trawick [EMAIL PROTECTED] wrote:
The ScriptSock directive must be used when there are two instances of
the server with same ServerRoot. If it is
On Sat, 20 Nov 2004 12:11:34 -0500, Jeff Trawick [EMAIL PROTECTED] wrote:
The ScriptSock directive must be used when there are two instances of
the server with same ServerRoot. If it is omitted, symptoms may
include
. wrong credentials for CGIs
. CGIs stop working for one server when other
* Jeff Trawick [EMAIL PROTECTED] wrote:
code to check for the misconfiguration is small and is expected to be
fool-proof (independent of what the user does); also, no way the
change can result in stale unix sockets left around, unlike sticking
the pid in the filename
see patch in
The ScriptSock directive must be used when there are two instances of
the server with same ServerRoot. If it is omitted, symptoms may
include
. wrong credentials for CGIs
. CGIs stop working for one server when other server is terminated
It should be easy to avoid this configuration requirement
