httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <>
Subject Re: mod_cgid, unix socket, ScriptSock directive
Date Tue, 23 Nov 2004 17:44:15 GMT
On Tue, 23 Nov 2004 12:18:11 -0500, Bill Stoddard <> wrote:
> Jeff Trawick wrote:
> > On Sat, 20 Nov 2004 12:11:34 -0500, Jeff Trawick <> 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 server is terminated
> >>
> >>It should be easy to avoid this configuration requirement by appending
> >>parent pid to the name of the unix socket which is used *when user
> >>didn't specify ScriptSock*, though there is slight migration concern
> >>in case administrator relies on name of unix socket for other reason
> >>(e.g., to use its existence as knowledge that mod_cgid is ready for
> >>business).
> >>
> >>It should be easy to catch such a misconfiguration by adding the
> >>parent pid to the CGI request sent over the Unix socket, and fail the
> >>request (and log appropriate message) if parent pid is wrong.
> >
> >
> > 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 attachment
> Definitely +1 in concept. This will save someone a -lot- of time if they don't have a
clue why their CGIs are
> failing and this is the problem.

I'm disappointed that configuration will still be required, but
mod_cgid shouldn't be trying to solve such a configuration issue like
automatically that when we're still left with LockFile and PidFile and
logs and mutexes which have the same issue.  (A more global approach
could be useful however.)

View raw message