Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=eZ8IlogLNJmfng+i9sJDw2NtMx1AKD66Ez6oYLnhgLOvSU/6R7jHHyBQ0wtqq4cc;
  h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Message-ID: 
 <24584763.1200807794210.JavaMail.root@elwamui-sweet.atl.sa.earthlink.net>
Date: Sat, 19 Jan 2008 21:43:14 -0800 (GMT-08:00)
From: c chan <cchan19933@earthlink.net>
Reply-To: c chan <cchan19933@earthlink.net>
To: modperl@perl.apache.org
Subject: Re: question on startup.pl overriding perl search path
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


-----Original Message-----
>From: Adam Prime <adam.prime@utoronto.ca>
>Sent: Jan 18, 2008 6:22 AM
>To: c chan <cchan19933@earthlink.net>
>Cc: modperl@perl.apache.org
>Subject: Re: question on startup.pl overriding perl search path
>
>c chan wrote:
>> I use "PerlConfigRequire /var/www/html/mypath/startup.pl" in httpd.conf to recompile all the CGIs. Inside startup.pl, I added the line:
>> 
>>   use lib qw(. mylib);
>> 
>> To me amazement, after all the CGI is precompiled, they start to look into the "." and "mylib" path for loading Perl Modules without even having the line [use lib qw(. mylib);] incorporated in each individual cgi script. 
>> 
>> Can someone explain to me why this is the case? Is the mod_perl startup.pl script simply becomes the parent apache process for all the preloaded CGIs?
>
>This is normal.  Under mod_perl the perl interpreter just keeps running 
>until the apache child dies your modified @INC stays modified.  I'm sure 
>someone with a better understanding of the internals can give a more 
>detailed 'why'.  FYI though, you should probably use PerlPostConfigRequire
>
>http://perl.apache.org/docs/2.0/user/config/config.html#C_PerlPostConfigRequire_
>
>> If I remove mod_perl, can I use the 
>> 
>>   PerlSetEnv -I/var/www/html/mypath -I/var/www/html/mypath/lib 
>> 
>> to achieve the same result.
>
>Isn't PerlSetEnv part of mod_perl?  In which case, no that wouldn't work 
>if you'd removed mod_perl
Thank you for your clarification. To make the CGI scripts both work under Apache and mod_perl, I put the "use lib qw(...);" in everyone of them.

- Clement 
>
>> This will make a profound effect on my CGI directory because whatever I installed will no longer affect the system perl module search path. In effect, this will make my application self contained and making trouble shooting make easier.
>> 
>> - C Chan
>
>Adam