On 8/28/2012 1:50 PM, Jeff Trawick wrote:
So under 2.2, I used --enable-cgi. I'll assume this statically built in mod_cgi.On Tue, Aug 28, 2012 at 1:21 PM, Kevin A. McGrail <KMcGrail@xxxxxxxx> wrote:On 8/28/2012 12:30 PM, Jeff Trawick wrote:Are you using mod_cgid or mod_cgi with 2.0 and 2.2?Aha! No, I don't think so, no. Spot checking a 2.2 server, I do not have mod_cgi(d). However, on this 2.4 server, I do have mod_cgid enabled right now because without it, my cgis were not being processed. Admittedly this is still a bit of a test server because I'm still working with mod_perl to get it to work with 2.4.X. So is it now required to run CGIs under 2.4 with mod_cgi(d) but that wasn't the case under 2.2/2.0? Or is there some other plugin or addhandler statement I should be using?httpd 2.x on Unix: Use mod_cgid if using a threaded MPM. Use mod_cgi or mod_cgid if using a non-threaded MPM. (Simpler is better, so choose mod_cgi.) IIRC, the default MPM changed from non-threaded in 2.2 (prefork) to threaded in 2.4 (event).
Under 2.4, I have a DSO for mod_cgid enabled because I do have a event MPM. But fundamentally, this means I was using mod_cgi for 2.2.So is this lack of stderr capturing to separate VHs expected behavior with 2.4? with mod_cgid?
If so, we likely need to update the error_log notes. But I'm still not sure if I've configured something wrong, if this is a bug or if this is a fairly undocumented change with 2.4.
Regards, KAM --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|