Steffen wrote:
mod_perl on Windows 2.2.7
Using http://theoryx5.uwinnipeg.ca/ppms/ with ActivePerl 5.8.8.822 FAILS
Rebuilding mod_perl with latest SVN snapshot 2.0.4-dev against 2.2.7
and use *only* the new generated mod_perl.so, it is working except from
command line.
Since this problem (bug 43534) is very sensitive to how Apache is started
I don't know which is best: make a new patch for it, or just tell
everyone they need to run Apache as a service if they want to use mod_perl.
I'd be happy to see a fix; yes I consider 'as a console' to be a test
environment, but I also consider it to be very useful and worth fixing.
Even the hack to stop a console httpd by-pid is still in status waiting
for a patch, as an Enhancement bug. So I won't say "no" to fixing.
Test results:
* Apache 2.2.7 started as a Windows Service
WORKS OK
Whew, cool.
* Apache 2.2.7 started from command-line
httpd.exe
FAILS - error.log has
[Sat Jan 05 12:08:42 2008] [notice] Parent: child process exited with
status 9 -- Restarting.
So we are looking why we arrived an exit(9) - it corresponds to
none of the APEXIT_* codes. Certainly not APEXIT_CHILDINIT nor
APEXIT_INIT which we would expect in the mpm.
I can't find a single example in servers/ or modules/ which would
lead to this result, which tells me is must be modperl or perl.
* Apache 2.2.7 started as single process from command-line
httpd.exe -X
WORKS OK
Now that's a little nutty. Would expect -X case to mirror the
other command line case. Good clues.
Bill
