I noticed during some testing there are a number of SLURM_* variables that are
not passed from the prolog's environment to the task-prolog's environment and
further into the job's environment. eg. SLURM_PARTITION, SLURM_JOB_GID etc....
Is there a way to force these variables to be passed along to each subsequent
environment?
Also is there a SLURM_CLUSTER or SLURM_CLUSTER_NAME variable that can be
"enabled"?
Currently running 2.6.3.
Thanx
-dave
--
David Kemeza 301.286.7741
NASA Center for Climate Simulation david.kem...@nasa.gov
Goddard Space Flight Center Code 606.2
"Unix is user friendly, it's just picky about its friends."
