Thanks for looking at it.
I prefer "%ENV = ();" in PerlCleanupHandler handler. (as i don't have to
modify so many scripts).
I don't think it has any negative effect ...
-Niraj
> -----Original Message-----
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 26, 2000 3:32 PM
> To: Niraj Sheth
> Cc: [EMAIL PROTECTED]
> Subject: RE: env in background process
>
>
> On Tue, 15 Aug 2000, Niraj Sheth wrote:
>
> > so why dump_env is getting both?
> > If I either uncomment "local %ENV = %ENV;" in script or put
> "%ENV = ();"
> > in PerlCleanupHandler then dump_env is working fine.
> > I tried both Apache::PerlRun and Apache::Registry which same result.
>
> oh whoops, you did send a test case. i think the problem is
> that mod_perl
> only clears the Perl side of %ENV, so the underlying C
> environ array is
> not modified. if we do that than other problems pop up. the best
> approach for the moment is to use:
>
> local $ENV{FOO1} = 'foo1';
>
> print `dump_env`;
>
