Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

mod_perl Installation Instructions

posted by Krow on 11:56 PM May 9th, 2002   Printer-friendly   Email story
Hi, today I had to install our 'in-progess' slash-site on another machine.
This machine, to say the least, was kind of methusalem and the installed packages, as far as slash is concerned, likewise.

After nearly three ours upgrading I had to decide to rebuild the only thing that's fairly new: Apache, or install mod_perl as dso.

The Installation Intructions warned me to do anything like this by stating that building mod_perl any other then the described way may break slash.

Useless to say that I installed it as dso :-)

Anything runs fine so far! Why this warning? What could possibly go wrong? What pittfalls lie ahead our way?

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • by Anonymous Coward
    The first time I installed slash, I kept on getting the perl script's text coming up, and not the actual page. Once I compiled Apache and mod_perl as instructed in INSTALL everything went okay. I'm guessing that this is one of the errors... maybe your site has a configuration that is already compatible, but the default for RedHat 7.2 was not correct...
    • You just missed out the perl-handler .pl line (not exact syntax, just something along those lines) from httpd.conf, from the sound of it. I've installed Slash on 2 Red Hat 7.2 default systems (with the appropriate updates from Red Hat applied) and they've worked fine without compiling Apache.