My point about switching the lines in startup.pl was to give you a
better understanding of what was going on. It was not intended as a fix.
Looks like you've got your base.pm package declaration right. But for
your sites to work as intended, you've got to do that for all the
modules in /ORIG/m
Hello,
What you're doing is not recommended as you run into namespace issues.
Perl caches files and modules that were loaded in %INC, so if you have
files and modules with the same name, only one of them gets loaded.
Possibly, as an exercise, if you switch the order of the ORIG and COPY
lines
Michael Peters wrote:
On 11/29/2011 10:29 PM, Nishikant Kapoor wrote:
I have been running a ModPerl site fine with following configuration.
The problem started when I made a complete copy of the original site and
tried to run the two in the same environment. For some reason, calling
up the ORIG
I ran similar tests to what Torsten had, and definitely noticed a
difference in memory usage, but didn't see any leaks in memory. Memory
usage is about twice when using $r->print, but it does hit it's max fairly
quickly. Memory usage also maxes out fairly quickly using the bucket
brigade method.
Oups... pressed the wrong key and sent it before I was done.
I guess the documentation on this page is not accurate then:
http://perl.apache.org/docs/1.0/guide/install.html#Testing_via_CGI_script
because I'm definitely NOT seeing GATEWAY_INTERFACE=CGI-Perl/1.1 (it's CGI/1.1).
Thanks a million!
> But try this :
> At the beginning of your script, add these lines :
>
> use Apache::RequestRec;
>
> my $r=shift;
> print "Hostname : ",$r->hostname,"\n";
>
> if you don't get an error, and you see the line in the output, then for sure
> you /are/
> running under mod_perl.
I did this and it g
Am 30.11.2011 um 15:02 schrieb Michael Peters:
> On 11/29/2011 10:29 PM, Nishikant Kapoor wrote:
>
>> I have been running a ModPerl site fine with following configuration.
>> The problem started when I made a complete copy of the original site and
>> tried to run the two in the same environment.
On 11/29/2011 10:29 PM, Nishikant Kapoor wrote:
I have been running a ModPerl site fine with following configuration.
The problem started when I made a complete copy of the original site and
tried to run the two in the same environment. For some reason, calling
up the ORIG site (http://127.0.0.1
