> As it turned out, the Ubuntu Apache2 install comes with both mod_cgi AND > mod_cgid installed and mod_cgid enabled. A-T apparently detects cgid and > tries using that in the config. The dies a horrible death because my > user (or nobody when runnung A-T as root) can't fire up and bind a new > cgid process when trying to run the cookies.pl test file. Once I > disabled mod_cgid (leaving mod_cgi) alone, all was well and all tests > passed.
hmm... ok, I don't know much about mod_cgid. so the questions I have are - is your setup somehow nonstandard? my 2.0.54 worker install defaulted to mod_cgid and I have no problems with any tests? - do you have problems with that same install and any of the cgi-based tests in the mod_perl test suite? > > So, was this just an unlucky happenstance on my machine, or should A-T > skip those tests if we have mod_cgid instead of mod_cgi? I'm not convinced that cgi versus cgid is the exact issue. it may be, but if I can run them but you can't then there's something else amuck. I'd think we need something like plan tests => 2, need [qw(CGI CGI::Cookie)], - need_cgi, need_lwp; + need_cgi, need_lwp, need_something_else; what that final condition might be is the key. if we can figure it out, we're in good shape. if it's something that only applies to mod_cgid and is global (like non-root users or somesuch) then I'd add it to the underlying conditions in need_cgi(). > I guess I > wasn't aware that need_cgi passed with cgid. yes, that's the basic idea. need_cgi is basically just asking "hey, do we have a cgi module around and activated" so you don't need to figure out whether it's mod_cgi or mod_cgid depending on your particular install. --Geoff
