It's funny you should ask that. I am actually dealing with issues around
that same problem right now. (I must admit I am running a fairly archaic
version of mod_perl -- 1.21 -- so I'd love to hear it if someone else has
newer information).
What I have discovered is that the %ENV variables are in no way permanent,
to avoid the problem you mention. In fact, they are removed at some point
after the server starts (perhaps after one execution on each thread?).
Therefore I run into the reverse problem -- %ENV entries are arbitrarily
empty when I need their values. My solution has been something like:
<Location "/mydir/">
PerlSetEnv ORACLE_HOME /oracle/home/
</Location>
which gets re-executed whenever any of those pages are hit.
This seems like a pretty inefficient solution to me -- better would be if
mod_perl simply gave each script a local copy of %ENV. Does anyone know a
better way to do it?
> -----Original Message-----
> From: martin langhoff [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 28, 2000 4:25 PM
> To: [EMAIL PROTECTED]
> Subject: manipulating %ENV
>
>
> hi,
>
> how safe is to manipulate %ENV in the context of an Embperl
> page under
> modperl? Does it get cleaned up or does it stay around?
>
> The qquestion is: is %ENV localized or do I face risks when altering
> its values?
>
>
>
>
> martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
