instead of invoking the script with #!/bin/bash try using source
scriptname to run it within the current shell. the #!/binbash
invokation spawns a subshell to run the script and the returns, blowing
away any environment variables you might have set.
-Mike
Right; fair discussion of this at
http://www.velocityreviews.com/forums/t352671-putenv.html
~ben
On Tue, Feb 26, 2008 at 11:25 AM, Mike Cherba
[EMAIL PROTECTED] wrote:
instead of invoking the script with #!/bin/bash try using source
scriptname to run it within the current shell. the
Rob Hudson wrote:
I've got some Python scripts that rely on shell environment variables
for certain things. I wrote a simple script that did an export but it
didn't take, and I'm guessing that the shell script gets its own
environment, that when the script terminates goes away.
Is there a way
On 2/26/08, Fred James [EMAIL PROTECTED] wrote:
... source the file as ...
. filename
That works for me. I'm mostly looking for a way to set those
variables and not have to remember the exact details every time.
Thanks,
Rob
___
EUGLUG mailing
Rob Hudson wrote:
On 2/26/08, Fred James [EMAIL PROTECTED] wrote:
... source the file as ...
. filename
That works for me. I'm mostly looking for a way to set those
variables and not have to remember the exact details every time.
Another popular technique is for the subprocess to
