perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: [mp2 bug] Perl*Env issues
Date Thu, 16 Dec 2004 20:16:16 GMT
Geoffrey Young wrote:
>>>PerlPassEnv HOME
>>>PerlPassEnv PORT
>>><Perl>
>>>$ServerRoot = $ENV{HOME} . "/web";
>>>$DocumentRoot = $ENV{HOME} . "/web/public" ;
>>>$Listen = $ENV{PORT};
>>></Perl>
>>
>>
>>Thanks for the example, Pratik. Now it's more clear to me.
>>
>>I propose the following "simple" solution:
>>
>>1) Keep %ENV intact at the server startup, so anything set in the shell
>>is seen from perl
> 
> 
> which would make the above PerlPassEnv directives unnecessary, right?  at
> least insofar as <Perl> sections are concerned?  that sounds fine to me.

Right. You will still want them if you need to get them after post_config 
phase.

>>2) PerlPassEnv and PerlSetEnv aren't run yet but postponed to until
>>after post_config.
>>3) just before starting workers, detach %ENV from environ, cleaning it
>>up completely. now run PerlPassEnv and PerlSetEnv from (2)
> 
> 
> nice.

I just need to check that Apache doesn't already nuke environ somewhere on 
the way.


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message