Skip to content
Snippets Groups Projects
Commit ad66d638 authored by Brian Christiansen's avatar Brian Christiansen
Browse files

Merge pull request #100 from paran1/slurm-14.03

Improve "Prolog and Epilog Scripts" in slurm.conf(5)
parents 7644f970 a75686fb
No related branches found
No related tags found
No related merge requests found
...@@ -3743,12 +3743,13 @@ NOTE: Standard output and error messages are normally not preserved. ...@@ -3743,12 +3743,13 @@ NOTE: Standard output and error messages are normally not preserved.
Explicitly write output and error messages to an appropriate location Explicitly write output and error messages to an appropriate location
if you wish to preserve that information. if you wish to preserve that information.
NOTE: The Prolog script is ONLY run on any individual NOTE: By default the Prolog script is ONLY run on any individual
node when it first sees a job step from a new allocation; it does not node when it first sees a job step from a new allocation; it does not
run the Prolog immediately when an allocation is granted. If no job steps run the Prolog immediately when an allocation is granted. If no job steps
from an allocation are run on a node, it will never run the Prolog for that from an allocation are run on a node, it will never run the Prolog for that
allocation. The Epilog, on the other hand, always runs on every node of an allocation. This Prolog behaviour can be changed by the
allocation when the allocation is released. \fBPrologFlags\fR parameter. The Epilog, on the other hand, always
runs on every node of an allocation when the allocation is released.
If the Epilog fails (returns a non\-zero exit code), this will result in the If the Epilog fails (returns a non\-zero exit code), this will result in the
node being set to a DRAIN state. node being set to a DRAIN state.
...@@ -3791,14 +3792,13 @@ SLURM_ARRAY_JOB_ID with SLURM_ARRAY_TASK_ID ...@@ -3791,14 +3792,13 @@ SLURM_ARRAY_JOB_ID with SLURM_ARRAY_TASK_ID
(e.g. "scontrol update ${SLURM_ARRAY_JOB_ID}_{$SLURM_ARRAY_TASK_ID} ..."); (e.g. "scontrol update ${SLURM_ARRAY_JOB_ID}_{$SLURM_ARRAY_TASK_ID} ...");
Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only. Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only.
.TP .TP
\fBSLURM_CLUSTER_NAME\fR
Name of the cluster executing the job.
.TP
\fBSLURM_JOB_ACCOUNT\fR \fBSLURM_JOB_ACCOUNT\fR
Account name used for the job. Account name used for the job.
Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only. Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only.
.TP .TP
\fBSLURM_JOB_CLUSTER_NAME\fR
Name of the cluster executing for the job.
Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only.
.TP
\fBSLURM_JOB_CONSTRAINTS\fR \fBSLURM_JOB_CONSTRAINTS\fR
Features required to run the job. Features required to run the job.
Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only. Available in \fBPrologSlurmctld\fR and \fBEpilogSlurmctld\fR only.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment