?
Alex
--
Alex Harper
Configuration Management
[EMAIL PROTECTED]
Use whatever you think of first -- Larry Wall
-Original Message-
From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 01, 2001 11:43 PM
To: Alex Harper
Cc: [EMAIL PROTECTED]
Subject: Re: CGI.pm params
--
Alex Harper
Configuration Management
[EMAIL PROTECTED]
Use whatever you think of first -- Larry Wall
I actually forgot to mention that we had tried it with my $cgi and
$cgi. Neither worked.
As for switching to Apache::Request, no can do. We need to maintain
mod_cgi compatibility for at least a few more months.
Alex
--
Alex Harper
Configuration Management
[EMAIL PROTECTED]
Use whatever you
(StartServers 2) and I removed the
CGI.pm precompile from the mod_perl startup.
Any other suggestions? I'm feeling a bit desperate...
Alex
--
Alex Harper
Configuration Management
[EMAIL PROTECTED]
Use whatever you think of first -- Larry Wall
handlers seem to fail (at least in this case).
Daniel, thanks for pointing me in the right direction!
Alex
--
Alex Harper
Configuration Management
[EMAIL PROTECTED]
Use whatever you think of first -- Larry Wall
-Original Message-
From: Daniel [mailto:[EMAIL PROTECTED]]
Sent: Monday
, October 1, 2001 7:42 PM
To: Perrin Harkins
Cc: Alex Harper; [EMAIL PROTECTED]
Subject: Re: CGI.pm params not being cleared?
Did you compile mod_perl with PERL_STACKED_HANDLERS?
Perrin Harkins wrote:
Alex Harper wrote:
Aha! That's where the problem lies. I had recently added
per-application list of lib paths, but that fixes us until I get
to see what mod_perl 2.0 has in store for me :-)
Thanks again for all the responses,
Alex
-Original Message-
From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 8:06 AM
To: Alex Harper
I understood the limitation of the single interpreter, the
problem again
was to append to @INC per VirtualHost.
It's confusing when you say that, since there's only one @INC for
everything. I'm interpreting this as meaning that you have a bunch of
applications with different install
mod_perl 2.0 has solved these problems already, but it's not in
production yet :)
Well that give me something to look forward to :-)
Have you read this one?
http://perl.apache.org/guide/config.html#Is_There_a_Way_to_Modify_INC_o
n
You probably need to
to modify the path to the startup and the path to
lib on the basis of the VirtualHost and I'd like to avoid hardcoding the
paths.
Thanks,
Alex
--
Alex HarperBroadJump, Inc.
[EMAIL PROTECTED]Configuration Manager
10 matches
Mail list logo