Paul Silevitch <p...@silevitch.com> writes: > Scott, > > I had a similar problem and I used Env::C to get around it. Definitely read > the perldoc to see the gotchas with this module. > > Let me know if it works for you,
Yeah, Env::C was the solution, thanks! It would be very nice to make this clearer in the docs, especially the migration guide on the Web site. Mentioning clearly that %ENV is no longer tied the to the real environment, that this affects child processes (not just C code), and that Env::C offers a solution would have saved me several hours. I would be happy to provide some suggested text for: http://perl.apache.org/docs/2.0/user/porting/compat.html#Issues_with_Environment_Variables if it would be helpful. ----Scott. > On Wed, Jun 3, 2009 at 2:58 AM, Scott Gifford <sgiff...@suspectclass.com> > wrote: > > [ also posted on PerlMonks ] > > I'm working on porting some code that's been running on mod_perl 1 for > a very long time to mod_perl 2. Mostly things have gone smoothly, but > I'm having trouble with environment variables. Sometimes my scripts go > off and run other scripts, and expect to be able to set things like > $ENV{PATH} for the child processes. However, for some reason under > mod_perl 2, my environment variables aren't getting passed to child > processes! Quite bizarre. [...]