«

Why wouldn't this work?
~
#!/bin/bash

MNT=/mnt/sdb5
JAVA_HOME=${MNT}/JApps/jdk/jdk1.6.0_01
export JAVA_HOME
echo $JAVA_HOME

PATH=${JAVA_HOME}/bin:$PATH
export PATH
echo $PATH

TOMCAT_HOME=/mnt/sdb5/JApps/tc/apache-tomcat-6.0.10
export TOMCAT_HOME
echo $TOMCAT_HOME
~
root@0[kd]# ls -l *.sh
-rwxr-xr-x 1 root root 241 May 4 16:51 javakpath00.sh
~
root@0[kd]# which bash
/bin/bash
~
root@0[kd]# bash -version
GNU bash, version 3.00.16(1)-release (i386-pc-linux-gnu)
Copyright (C) 2004 Free Software Foundation, Inc.
~
lbrtchx

In article <. com>,
<> wrote:
> Why wouldn't this work?
> ~
> #!/bin/bash
>
> MNT=/mnt/sdb5
> JAVA_HOME=${MNT}/JApps/jdk/jdk1.6.0_01
> export JAVA_HOME
> echo $JAVA_HOME

[ snip ]

Executing a script in the normal way (./thescript, for example)
creates a subshell, and any environment variables you set are
set for the subshell -- and not passed back to the parent shell.
Hence your script has no effect on its caller's environment
variables.

To get the effect I think you want, you need to instead "source"
the script. If you're also using bash as your interactive
shell, you'd say

source ./thescript

or

. ./thescript

--
B. L. Massingill
ObDisclaimer: I don't speak for my employers; they return the favor.