On Tue, Aug 30, 2005 at 05:25:07PM +0100, Joe Orton wrote:
> > This has all sorts of consequences, the most annoying of which is that
> > both "stop" and "graceful-stop" actually won't kill CGI processes when
> > using a threaded MPM/cgid.
>
> So is mod_cgid still the default CGI module for worker because there
> once existed some ye-olde-Unixes which had an "interesting" fork()
> implementation? Given that POSIX has mandated since 2001 or whatever
> that fork() duplicates only the calling thread, is there any
> disadvantage to using mod_cgi in all MPMs on modern platforms?
Can't think of any, and performance is easy to measure.
Either way, might be worth doing something like;
http://people.apache.org/~colm/cgid-kill-children.patch
in cgid itself, to help fix the immediate problem. Of course that patch
won't help with suexec CGI's, since the daemon won't have permission to
send the child a signal.
--
Colm MacCárthaigh Public Key: [EMAIL PROTECTED]
