Brain-dead simple Apache 2.0/mod_ssl/mod_perl build HOWTO for RH Linux. Has a Subversion appendix if you need source control. I've been using this setup for over a year on a medium-ish (~1000 user) production site. Maybe it can help...

http://shaderlab.com/mod_perl/server_mod_perl_config.txt

y


Tom Williams wrote:


Stas Bekman wrote:

Sorry Raf, but you put yourself into a bad position. 1.99_09 is 1 year old and many bugs that you are encountering now have been solved long time ago. We can't support older Apaches, because they have changed a lot of things since 2.0.43 and it won't work. So I can't offer much of an advice but to figure out how to move to at least 2.0.46.

Apache 2.0.43 has its own load of normal and security problems which were fixed long time ago. Sticking to the old buggy version doesn't make much sense.

The only idea I could offer to you is this: Keep Apache 2.0.43 as a front-end, and put Apache 2.0.49 with the latest mp2 on the backend. So your testers are still happy and you use 2.0.49 only to serve mp2 content. The docs on perl.apache.org have tons of info on how to set such a beast up (even though in mp1 section, but it should work all the same).


Thanks for the info. I'm in a similar situation where I'm running Apache/2.0.48 (Unix) mod_perl/1.99_13 Perl/v5.8.2 PHP/4.3.5 on a RedHat 9 Linux box and I want to upgrade to perl 5.8.4 but I can't get the multi-threaded perl to pass the test suite. :( The "wait" test in the perl thread test suite fails. Would perl 5.8.2 be sufficient to support MP2 when the first stable release is out? I'm also running the "worker" Apache 2 MPM.

Thanks....

Peace...

Tom


-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to