Title: Re: [slurm-dev] Getting job environment
Naively, you could always add an echo $var > somefile to your
sbatch and review the output after the job started, to verify that
$var is set correctly.
Usualy, one can use --export or --get-user-env switches in sbatch to
force environment propagation to jobs.
from sbatch man:
- --export=<environment variables | ALL | NONE>
-
Identify which environment variables are propagated to the batch
job.
Multiple environment variable names should be comma separated.
Environment variable names may be specified to propagate the
current
value of those variables (e.g. "--export=EDITOR") or specific
values
for the variables may be exported (e.g..
"--export=EDITOR=/bin/vi")
in addition to the environment variables that would otherwise be
set.
This option particularly important for jobs that are submitted
on one cluster
and execute on a different cluster (e.g. with different paths).
By default all
environment variables are propagated. If the argument is NONE
or
specific environment variable names, then the --get-user-env
option will implicitly be set to load other environment
variables based upon
the user's configuration on the cluster which executes the job.
On 15/12//2015 19:47, Oliver Freyermuth
wrote:
Dear SLURMers,
I would like to check whether some jobs in our queue have been submitted with correct environment variables.
Is there any way to check / print the environment for submitted (pending or running) jobs?
Cheers,
Oliver
|
smime.p7s
Description: S/MIME Cryptographic Signature
