Fabian,
I think you are misinterpreting your example.
The shell replaces "$VARIABLE" before globus-job-run is called.
To find out the environment available for job executables, try this:
$ globus-job-run machine_name /usr/bin/printenv
You will find the default environment is very limited. There are
provisions for setting the environment, either from the command line
or in a job description file.
Cheers!
On 21.05.08, Fabian Lueghausen wrote:
> Hey list !
>
> I've got a question concerning the environment variables used when
> executing the globus-job-run command.
>
> When submitting a job from my local machine "mertens" to a remote
> machine "ingrid", the remote machine is always using my local
> environment variables (wherefore...)
>
> For example:
>
> [EMAIL PROTECTED] ~]$ *globus-job-run ingrid /bin/echo $VARIABLE*
> VARIABLE: Undefined variable.
> [EMAIL PROTECTED] ~]$ setenv VARIABLE "hello world!"
> [EMAIL PROTECTED] ~]$ globus-job-run ingrid /bin/echo $VARIABLE
> hello world!
> [EMAIL PROTECTED] ~]$
>
> This becomes a problem while a want to start a programm whose runtime
> environment variables should be defined on the remote machine because
> they differ from the ones which should be used on my local machine...
>
> So my question: Is there any way to set some variables on the remote
> machine?
>
> Great *thanks* for all your answers!
> Fabian
- - - - - - - - - - - - - - - - - - - - - - - - -
Steve White +49(331)7499-202
e-Science / AstroGrid-D Zi. 35 Bg. 20
- - - - - - - - - - - - - - - - - - - - - - - - -
Astrophysikalisches Institut Potsdam (AIP)
An der Sternwarte 16, D-14482 Potsdam
Vorstand: Prof. Dr. Matthias Steinmetz, Peter A. Stolz
Stiftung privaten Rechts, Stiftungsverzeichnis Brandenburg: III/7-71-026
- - - - - - - - - - - - - - - - - - - - - - - - -
