On Wed, 25 Oct 2000, gene wrote:
I tried installing apache-1.3.14-2mdk and
apache-mod_perl-1.3.14_1.24-2mdk from cooker 7.2 beta last night.
mod-perl is compiled directly into apache-mod_perl which runs as a
proxy server alongside vanilla apache in this setup, unlike what I
had been using where mod_perl was a loadable module in the main
apache. Anyway, I couldn't get this new set up to work. When I
tried to access a perl script, the server started spawning a huge
number of threads that ground the computer to a halt. I tried to
down-grade back to my old setup, but couldn't get that working, so
right now I'm running mod_perl-less.
You don't have to run mod_perl as a proxy. If you install both apache and
apache-mod_perl, it runs as a proxy, but if you remove apache, you will
get a straight apache+mod_perl server, with no SGI optimizations and
FrontPage, and no SSL.
I did this because there were so much conflicts in the patches that you
wouldn't believe it. Using mod_perl as a module makes the server crash
with Apache-ASP and HTML-Embperl.
My setup is standard, as it's based on the mod_perl optimization pages on
perl.apache.org.
My questions are:
Have other people gotten this setup to work?
It works for most people. Maybe in the upgrade process, your config files
got messed up. Remove all your Apache packages, rm -rf /etc/httpd, and
re-install. Make sure you also re-install mm, the shared memory lib that
Apache uses.
Jean-Michel Dault [EMAIL PROTECTED]
MandrakeSoft inc, Montreal (Canada)
HTCPCP/1.0 Developper (http://www.ietf.org/rfc/rfc2324.txt)
Keep in touch with http://mandrakeforum.com:
Subscribe the "[EMAIL PROTECTED]" mailing list.
