Bill Hudson wrote:
To be honest what you sent me is over my head.
Did you read the docs that I linked to? What part of this is over your head?
"To determine if you can use a DSO mod_perl with your version of Perl, first
find out which malloc your Perl was built with by running:
% perl -V:us
Car54 wrote:
I'm very new at this and I already have apache installed and I just want
to
be sure that when I install it again it doesn't cause a problem with the
software I have on the server that depends on it, along with being
installed
at the proper location.
I recommend compiling mod_pe
Brian Gaber wrote:
The HTML code that I am selecting looks like this:
That's not necessary. What does your perl code look like now? Also, try
printing/warning the value of $$, which is the process ID. I think you'll
find that the value of your variable stays the same for each process.
Michael Peters wrote:
Brian Gaber wrote:
Using $q was not successful.
That's because you ignored my advice :)
Here is what I have done:
use vars qw($q);
That makes $q a global. Bad, bad, very bad. Slap yourself on the wrist.
Remove
that "use vars" line.
I don't see what is so bad abou
Maybe you need to use PerlSetEnv ?
- Original Message -
From: "Rob French" <[EMAIL PROTECTED]>
To: "André Warnier" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, March 19, 2008 2:41 PM
Subject: Re: [mp1] Can't get UTF8 input streams to automatically be decoded
using PERL_UNICODE under mod_p
Try PerlSetEnv instead :)
- Original Message -
From: "Tad Johnston" <[EMAIL PROTECTED]>
To: "Tad Johnston" <[EMAIL PROTECTED]>
Cc: "Adam Prime" <[EMAIL PROTECTED]>;
Sent: Friday, December 21, 2007 9:06 PM
Subject: Re: PerlAccessHandler problems
Correction*
SetEnv PROXY_BIND localho
Hopefully you have apxs installed which you can use to build mod_perl
without Apache sources. I have done this on Linux and worked perfectly even
when other methods didn't work for some reason.
Here are the instructions
http://perl.apache.org/docs/1.0/guide/install.html#Build_mod_perl_as_a_DSO_
Where is your DBI "connect" method? Do you have error checking in place in
case the connect fails? If the connect fails, your database handle will be
undef.
Try adding
or die DBI->errstr;
to your connect method as well as the prepare on line 1059.
- Original Message -
From: Dustin
Try using PerlResponseHandler ModPerl::PerlRun, or ModPerl::PerlRunPrefork
(if you use the preforking Apache MPM) and see what happens. You might have
to install it first if it wasn't already installed.
- Original Message -
From: pubert na
To: modperl@perl.apache.org
Sent: Thursday,
