Proper SYNTAX for EXPORTing variables

[Michael Steele_2]

Hi:

ScritA calls ScriptB

In ScriptA
SERVER="mecury"
export SERVER

In ScriptB
echo $SERVER

And it prints nada.

What up?

[Doug O'Leary]

Hey;

Works for me...

$ cat A B
#!/bin/ksh

Server="mercury"
export Server

./B
#!/bin/ksh

echo $Server
$ ./A
mercury

You sure you're not stomping SERVER somewhere in ScriptB?

Doug

[Pete Randall]

What shell are you using?


Pete

[James R. Ferguson · Accepted solution]

Hi:

Source 'ScriptA' so that a separate environment isn't created for it:

# . ./ScriptA
# ./ScriptB

...or for that matter, *within* 'ScriptB' do:

...
. ./ScriptA
...

Note that shell sourcing is done with a dot, followed by whitespace, followed by the script name.

Regards!

...JRF...

[Dennis Handly]

>SERVER="mecury"
>export SERVER

This is the old borne shell way of doing things. In a real shell you can use:
export SERVER="mecury"

[Steven Schweda]

Note that, as usual, showing an actual
failing test case instead of a vague
description ("ScritA calls ScriptB", where
"calls" is not well defined) would make this
problem easier to diagnose with less reliance
on guesswork/intuition.

Just a thought.