lets say i have one script which initializes system variables.
So it looks something like this:

#!/bin/bash
VAR1="etc/dir1"
export VAR1
VAR2="etc/dir2"
export VAR2


I want to call this script from another script and initialize variables this
way.
Right now I'm trying this.

#!/bin/bash
cd to the directory of the first script
source ./script1


After I check variables by running ENV command I don't see them
so something is obviously not working.

Variables do get set if i simply run ./script one from the command line
though.

"asdf" <asdf@asdf.com> writes:

>lets say i have one script which initializes system variables.
>So it looks something like this:

>#!/bin/bash
>VAR1="etc/dir1"
>export VAR1
>VAR2="etc/dir2"
>export VAR2


>I want to call this script from another script and initialize variables this
>way.

You cannot do so. variables are not inherited by parents.
You can source a file in which the variables are defined however.

source firstfile
in the second.

(See examples in /etc/init.d)


>Right now I'm trying this.

>#!/bin/bash
>cd to the directory of the first script
>source ./script1


>After I check variables by running ENV command I don't see them
>so something is obviously not working.

Sure they are. Try
echo $VAR1
in that second script. Note that these variable will NOT be defined in the
parent (eg console)


>Variables do get set if i simply run ./script one from the command line
>though.

"Unruh" <unruh-spam@physics.ubc.ca> wrote in message
news:dX%Li.35280$nO3.9507@edtnps90...
> "asdf" <asdf@asdf.com> writes:
>
>>lets say i have one script which initializes system variables.
>>So it looks something like this:
>
>>#!/bin/bash
>>VAR1="etc/dir1"
>>export VAR1
>>VAR2="etc/dir2"
>>export VAR2
>
>
>>I want to call this script from another script and initialize variables
>>this
>>way.
>
> You cannot do so. variables are not inherited by parents.
> You can source a file in which the variables are defined however.
>
> source firstfile
> in the second.
>
> (See examples in /etc/init.d)
>
>
>>Right now I'm trying this.
>
>>#!/bin/bash
>>cd to the directory of the first script
>>source ./script1
>
>
>>After I check variables by running ENV command I don't see them
>>so something is obviously not working.
>
> Sure they are. Try
> echo $VAR1
> in that second script. Note that these variable will NOT be defined in the
> parent (eg console)

so how do I define them within the script so that they are retained in the
console?

thank you
>
>
>>Variables do get set if i simply run ./script one from the command line
>>though.
>
>

"asdf" <asdf@asdf.com> writes:


>"Unruh" <unruh-spam@physics.ubc.ca> wrote in message
>news:dX%Li.35280$nO3.9507@edtnps90...
>> "asdf" <asdf@asdf.com> writes:
>>
>>>lets say i have one script which initializes system variables.
>>>So it looks something like this:
>>
>>>#!/bin/bash
>>>VAR1="etc/dir1"
>>>export VAR1
>>>VAR2="etc/dir2"
>>>export VAR2
>>
>>
>>>I want to call this script from another script and initialize variables
>>>this
>>>way.
>>
>> You cannot do so. variables are not inherited by parents.
>> You can source a file in which the variables are defined however.
>>
>> source firstfile
>> in the second.
>>
>> (See examples in /etc/init.d)
>>
>>
>>>Right now I'm trying this.
>>
>>>#!/bin/bash
>>>cd to the directory of the first script
>>>source ./script1
>>
>>
>>>After I check variables by running ENV command I don't see them
>>>so something is obviously not working.
>>
>> Sure they are. Try
>> echo $VAR1
>> in that second script. Note that these variable will NOT be defined in the
>> parent (eg console)

>so how do I define them within the script so that they are retained in the
>console?

Teh only way is to source the script.


>thank you
>>
>>
>>>Variables do get set if i simply run ./script one from the command line
>>>though.
>>
>>

asdf <asdf@asdf.com>:
> lets say i have one script which initializes system variables.
> So it looks something like this:
>
> #!/bin/bash
> VAR1="etc/dir1"
> export VAR1
> VAR2="etc/dir2"
> export VAR2
>
> I want to call this script from another script and initialize
> variables this way. Right now I'm trying this.
>
> #!/bin/bash
> cd to the directory of the first script
> source ./script1

That should be fine, and script1 should find them set.

> After I check variables by running ENV command I don't see them
> so something is obviously not working.

You won't see them in your current environment. Their parent-->child
relationship has nothing to do with your environment. Feature! :-)

> Variables do get set if i simply run ./script one from the command
> line though.

Again, correct behaviour. Now they're defined in your own shell's
environment. "set" shows you. Write a shell script that says:

#!/bin/bash
#
# yada.
#

env > /tmp/env.txt

exit 0

Now run ./script, then the above.

That'll show that child process inherited its parent's process
environment, without having to run ./script itself. Env. vars are not
global until you export them, and exporting them only affects child
processes. ... of the shell which exports them.

It gets a bit fuzzier when you're at the command line affecting your
existing environment, but there are no children involved there, so
inheritance rules don't apply.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.

asdf <asdf@asdf.com> wrote:
> lets say i have one script which initializes system variables.
> So it looks something like this:

This is script1:

> #!/bin/bash
> VAR1="etc/dir1"
> export VAR1
> VAR2="etc/dir2"
> export VAR2


> I want to call this script from another script and initialize variables this
> way.
> Right now I'm trying this.

This is script2:

> #!/bin/bash
> cd to the directory of the first script
> source ./script1

Do this at the command line:

source ./script2

and it will work. You will get a changed environment at the console.
The other poster was confused.

The source command causes a script to run in the current environment
instead of in its own shell. Because you use two scripts, you need two
instances of source.

-Joe

[The remainder of asdf's posting has been omitted.]

so I configured chkconfig to start sybstart server on levels 345

and it shows correctly in rc5.d and also starts up correctly

when i do 'service sybstart start'



As a way to error check I also modified script to output to a file
'sybstart'

the status of the server while the script is being executed during startup.

the 'sybstart' file shows that the script does run on startup and that the
server

is functional. However when i do 'showserver' command after startup it's not

running. I'm still not sure what's wrong but I feel it's something minor.



Thanks a bunch; the script is below.



#!/bin/bash
#chkconfig: 345 99 50
#description: sybase startup script



#source function library.
.. /etc/rc.d/init.d/functions
.. /opt/sybase/SYBASE.sh



start() {
/opt/sybase/ASE-15_0/install/startserver -f
/opt/sybase/ASE-15_0/install/RUN_sybase
/opt/sybase/ASE-15_0/install/showserver >> /home/homedir/sybstart



}



case "$1" in
start)
start
;;



stop)
stop

#function to be completed
;;



status)
status

#to be completed
;;



restart)

#to be completed
stop
start
;;
*)
esac





"Joseph H. Rosevear" <joe@airlink9.hopto.org> wrote in message
news:47032059$0$90270$14726298@news.sunsite.dk...
> asdf <asdf@asdf.com> wrote:
>> lets say i have one script which initializes system variables.
>> So it looks something like this:
>
> This is script1:
>
>> #!/bin/bash
>> VAR1="etc/dir1"
>> export VAR1
>> VAR2="etc/dir2"
>> export VAR2
>
>
>> I want to call this script from another script and initialize variables
>> this
>> way.
>> Right now I'm trying this.
>
> This is script2:
>
>> #!/bin/bash
>> cd to the directory of the first script
>> source ./script1
>
> Do this at the command line:
>
> source ./script2
>
> and it will work. You will get a changed environment at the console.
> The other poster was confused.
>
> The source command causes a script to run in the current environment
> instead of in its own shell. Because you use two scripts, you need two
> instances of source.
>
> -Joe
>
> [The remainder of asdf's posting has been omitted.]

asdf <asdf@asdf.com> wrote:
> so I configured chkconfig to start sybstart server on levels 345

> and it shows correctly in rc5.d and also starts up correctly

> when i do 'service sybstart start'



> As a way to error check I also modified script to output to a file
> 'sybstart'

> the status of the server while the script is being executed during startup.

> the 'sybstart' file shows that the script does run on startup and that the
> server

> is functional. However when i do 'showserver' command after startup it's not

> running. I'm still not sure what's wrong but I feel it's something minor.



> Thanks a bunch; the script is below.

[snip]

Sounds great. Keep up the good work.

-Joe