:[EMAIL PROTECTED]
Sent: Friday, August 15, 2008 3:15 PM
To: modperl@perl.apache.org
Cc: Berg, Eric
Subject: Re: mp2, IPC::Run3 Environment Variables giving
variable not set error
On Fri 15 Aug 2008, Berg, Eric wrote:
This issue of the environment variables' not being passed to forked
On Sat 16 Aug 2008, Berg, Eric wrote:
Now, the environment is a process global resource. So, if
those values are changed all threads are affected. This is surely
no what you want.
When you say that the environment is a global process, global to
what? Each forked process has its own
Environment Variables giving
variable not set error
On Fri 15 Aug 2008, Berg, Eric wrote:
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
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
On Fri 15 Aug 2008, Berg, Eric wrote:
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
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
