Hello All,
This isn't so much a development question as it is one about deployment.
I've built an application which runs with the latest and greatest mod_perl
and apache 2. It's just a run of the mill content handler which delegates
some stuff to Template.pm.
Now due to internal strictness I ha
Hello world,
I've a second issue which is really bugging me now. I've compiled
mod_perl against our server apache version, which happend to be 2.0.40. I
made a package with the perl modules and the apache/modules/mod_perl.so
for this.
On a server restart I keep getting:
"Cannot use threaded MPM
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
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 mu
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:
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
