On Wed, 2005-07-20 at 08:15 +0800, Jacob Jarick wrote:
> both, though modperl two at least has straight forward INSTALL file
> which tells u the lines to add. Ive read all 3 of those documents
> several times and I have tried the short examples. But to no avail -
Well, what you add here depends on how you compiled mod_perl (DSO or
static) and what you want it to do.
> whats the line u add for loading the perl module in apache 1.3 ? (if you
> followed the short 3 step guide).
I'm not sure what guide you're referring to there.
If you just want Apache::Registry to emulate CGI in a location
called /perl/, you add something as simple as what's in the "Getting
Your Feet Wet" document:
PerlModule Apache::Registry
<Location /perl/>
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
PerlSendHeader On
allow from all
</Location>
> I have modperl 2.0 working with apache thanks to INSTALL but the scripts
> fail randomly.
If you report the problem, someone may be able to help. See
http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
> From memory when I used to do alot more modperl setups in 1.3 shouldnt u
> have to add:
> the module loading line
Not unless you did some kind of specialized compile.
> Line that says execute .pl
If you want it to do that, yes. Use the Files directive, as described
in the docs I pointed to earlier.
> add index.pl to indexes
If you want to do that, it's pretty simple. Nothing mod_perl-specific.
Just use the standard DirectoryIndex stuff.
> and set execute perm on 1 of the dirs in the apache config
ExecCGI, as shown in those docs.
> if some1 can post a quick example and maybe update the online docs. They left
> me stumped Im afraid when it came to configuring the apache.conf
It's hard to tell what should be changed. The information you're asking
about is there, as far as I can see. Can you explain where you're
getting lost?
- Perrin
