Thanks again, Andre. This issue of the environment variables' not being passed to forked processes is turning into a fairly substantial problem for me. We have a number of places in our code -- both the modules that are tightly controlled and fairly easy to manage, as well as a bunch of scripts and CGI's that use them -- that use system or backticks (sometimes via IPC::Run3) to get info from external tools.
Does anybody know anything about this issue or about the code involved? How difficult would it be to address this? I took a look at the code in modperl_env.c as suggested in the docs, but I'm a Perl guy, not a C guy. This is a deal killer for us. I'd appreciate any comments on this. One option seems to be to pass the environment variables if we're not in a threaded (worker) server. Maybe that would work for us. Anybody? Thanks a lot. Eric. > -----Original Message----- > From: André Warnier [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2008 10:59 AM > To: modperl@perl.apache.org > Cc: Berg, Eric > Subject: Re: mp2, IPC::Run3 && Environment Variables giving > "variable not set" error > > Berg, Eric wrote: > [...] > I don't know the exact answer to your question, but assuming > you are in > a Unix environment, you could try the following : > > In a Unix-like environment, if you launch a command using the > following > form : > > VAR1=value1 VAR2=value2 command > > then VAR1 and VAR2 are automatically "exported" as > environment variables > for the program "command". > > Thus, if in your script you have the possibility to start > your external > command in that way, it may be a usable work-around to your problem. > > André > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -------- IRS Circular 230 Disclosure: Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.
