There are some SLURM_* variables that are set in the prolog's environment that are not carried through to the task-prolog, the job's, task-epilog, and epilog environments. These would be nice to have to be able to trigger of these variables at every level of the job setup and teardown. I'd like to see the following variables carried through the environment as it passes through the various phases. SLURM_CLUSTER or SLURM_CLUSTERNAME (I think would need to be added) SLURM_PARTITION This appears in the prolog and epilog environment but not in the task-prolog's or task-epilog's environment SLURM_JOB_USER only appears in prolog, task-epilog, and epilog
*** Ticket 519 has been marked as a duplicate of this ticket. ***
*** Ticket 518 has been marked as a duplicate of this ticket. ***
*** Ticket 520 has been marked as a duplicate of this ticket. ***
*** Ticket 517 has been marked as a duplicate of this ticket. ***
*** Ticket 516 has been marked as a duplicate of this ticket. ***
Browser problems... This is a dup of 521. -dave *** This ticket has been marked as a duplicate of ticket 521 ***