Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
2d4f8e58
Commit
2d4f8e58
authored
15 years ago
by
Don Lipari
Browse files
Options
Downloads
Patches
Plain Diff
Documented the -P to -d dependency option change to the salloc/sbatch/srun
man pages
parent
052c4e4a
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
doc/man/man1/salloc.1
+32
-32
32 additions, 32 deletions
doc/man/man1/salloc.1
doc/man/man1/sbatch.1
+32
-32
32 additions, 32 deletions
doc/man/man1/sbatch.1
doc/man/man1/srun.1
+39
-39
39 additions, 39 deletions
doc/man/man1/srun.1
with
103 additions
and
103 deletions
doc/man/man1/salloc.1
+
32
−
32
View file @
2d4f8e58
...
@@ -275,6 +275,38 @@ the \-\-cpus\-per\-task=3 options, the controller knows that each task requires
...
@@ -275,6 +275,38 @@ the \-\-cpus\-per\-task=3 options, the controller knows that each task requires
3 processors on the same node, and the controller will grant an allocation
3 processors on the same node, and the controller will grant an allocation
of 4 nodes, one for each of the 4 tasks.
of 4 nodes, one for each of the 4 tasks.
.TP
\fB\-d\fR, \fB\-\-dependency\fR=<\fIdependency_list\fR>
Defer the start of this job until the specified dependencies have been
satisfied completed.
<\fIdependency_list\fR> is of the form
<\fItype:job_id[:job_id][,type:job_id[:job_id]]\fR>.
Many jobs can share the same dependency and these jobs may even belong to
different users. The value may be changed after job submission using the
scontrol command.
.PD
.RS
.TP
\fBafter:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have begun
execution.
.TP
\fBafterany:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated.
.TP
\fBafternotok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated
in some failed state (non-zero exit code, node failure, timed out, etc).
.TP
\fBafterok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have successfully
executed (ran to completion with non-zero exit code).
.TP
\fBsingleton\fR
This job can begin execution after any previously launched jobs
sharing the same job name and user have terminated.
.RE
.TP
.TP
\fB\-D\fR, \fB\-\-chdir\fR=<\fIpath\fR>
\fB\-D\fR, \fB\-\-chdir\fR=<\fIpath\fR>
change directory to \fIpath\fR before beginning execution.
change directory to \fIpath\fR before beginning execution.
...
@@ -674,38 +706,6 @@ per processor. By specifying \fB\-\-overcommit\fR you are explicitly
...
@@ -674,38 +706,6 @@ per processor. By specifying \fB\-\-overcommit\fR you are explicitly
allowing more than one task per processor. However no more than
allowing more than one task per processor. However no more than
\fBMAX_TASKS_PER_NODE\fR tasks are permitted to execute per node.
\fBMAX_TASKS_PER_NODE\fR tasks are permitted to execute per node.
.TP
\fB\-P\fR, \fB\-\-dependency\fR=<\fIdependency_list\fR>
Defer the start of this job until the specified dependencies have been
satisfied completed.
<\fIdependency_list\fR> is of the form
<\fItype:job_id[:job_id][,type:job_id[:job_id]]\fR>.
Many jobs can share the same dependency and these jobs may even belong to
different users. The value may be changed after job submission using the
scontrol command.
.PD
.RS
.TP
\fBafter:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have begun
execution.
.TP
\fBafterany:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated.
.TP
\fBafternotok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated
in some failed state (non-zero exit code, node failure, timed out, etc).
.TP
\fBafterok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have successfully
executed (ran to completion with non-zero exit code).
.TP
\fBsingleton\fR
This job can begin execution after any previously launched jobs sharing the same
job name and user have terminated.
.RE
.TP
.TP
\fB\-p\fR, \fB\-\-partition\fR=<\fIpartition name\fR>
\fB\-p\fR, \fB\-\-partition\fR=<\fIpartition name\fR>
Request a specific partition for the resource allocation. If not specified,
Request a specific partition for the resource allocation. If not specified,
...
...
This diff is collapsed.
Click to expand it.
doc/man/man1/sbatch.1
+
32
−
32
View file @
2d4f8e58
...
@@ -283,6 +283,38 @@ the \-\-cpus\-per\-task=3 options, the controller knows that each task requires
...
@@ -283,6 +283,38 @@ the \-\-cpus\-per\-task=3 options, the controller knows that each task requires
3 processors on the same node, and the controller will grant an allocation
3 processors on the same node, and the controller will grant an allocation
of 4 nodes, one for each of the 4 tasks.
of 4 nodes, one for each of the 4 tasks.
.TP
\fB\-d\fR, \fB\-\-dependency\fR=<\fIdependency_list\fR>
Defer the start of this job until the specified dependencies have been
satisfied completed.
<\fIdependency_list\fR> is of the form
<\fItype:job_id[:job_id][,type:job_id[:job_id]]\fR>.
Many jobs can share the same dependency and these jobs may even belong to
different users. The value may be changed after job submission using the
scontrol command.
.PD
.RS
.TP
\fBafter:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have begun
execution.
.TP
\fBafterany:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated.
.TP
\fBafternotok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated
in some failed state (non-zero exit code, node failure, timed out, etc).
.TP
\fBafterok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have successfully
executed (ran to completion with non-zero exit code).
.TP
\fBsingleton\fR
This job can begin execution after any previously launched jobs
sharing the same job name and user have terminated.
.RE
.TP
.TP
\fB\-D\fR, \fB\-\-workdir\fR=<\fIdirectory\fR>
\fB\-D\fR, \fB\-\-workdir\fR=<\fIdirectory\fR>
Set the working directory of the batch script to \fIdirectory\fR before
Set the working directory of the batch script to \fIdirectory\fR before
...
@@ -717,38 +749,6 @@ Open the output and error files using append or truncate mode as specified.
...
@@ -717,38 +749,6 @@ Open the output and error files using append or truncate mode as specified.
The default value is specified by the system configuration parameter
The default value is specified by the system configuration parameter
\fIJobFileAppend\fR.
\fIJobFileAppend\fR.
.TP
\fB\-P\fR, \fB\-\-dependency\fR=<\fIdependency_list\fR>
Defer the start of this job until the specified dependencies have been
satisfied completed.
<\fIdependency_list\fR> is of the form
<\fItype:job_id[:job_id][,type:job_id[:job_id]]\fR>.
Many jobs can share the same dependency and these jobs may even belong to
different users. The value may be changed after job submission using the
scontrol command.
.PD
.RS
.TP
\fBafter:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have begun
execution.
.TP
\fBafterany:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated.
.TP
\fBafternotok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated
in some failed state (non-zero exit code, node failure, timed out, etc).
.TP
\fBafterok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have successfully
executed (ran to completion with non-zero exit code).
.TP
\fBsingleton\fR
This job can begin execution after any previously launched jobs sharing the same
job name and user have terminated.
.RE
.TP
.TP
\fB\-p\fR, \fB\-\-partition\fR=<\fIpartition name\fR>
\fB\-p\fR, \fB\-\-partition\fR=<\fIpartition name\fR>
Request a specific partition for the resource allocation. If not specified,
Request a specific partition for the resource allocation. If not specified,
...
...
This diff is collapsed.
Click to expand it.
doc/man/man1/srun.1
+
39
−
39
View file @
2d4f8e58
...
@@ -299,19 +299,44 @@ This option may also be useful to spawn tasks without allocating
...
@@ -299,19 +299,44 @@ This option may also be useful to spawn tasks without allocating
resources to the job step from the job's allocation when running
resources to the job step from the job's allocation when running
multiple job steps with the \fB\-\-exclusive\fR option.
multiple job steps with the \fB\-\-exclusive\fR option.
.TP
\fB\-d\fR, \fB\-\-dependency\fR=<\fIdependency_list\fR>
Defer the start of this job until the specified dependencies have been
satisfied completed.
<\fIdependency_list\fR> is of the form
<\fItype:job_id[:job_id][,type:job_id[:job_id]]\fR>.
Many jobs can share the same dependency and these jobs may even belong to
different users. The value may be changed after job submission using the
scontrol command.
.PD
.RS
.TP
\fBafter:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have begun
execution.
.TP
\fBafterany:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated.
.TP
\fBafternotok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated
in some failed state (non-zero exit code, node failure, timed out, etc).
.TP
\fBafterok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have successfully
executed (ran to completion with non-zero exit code).
.TP
\fBsingleton\fR
This job can begin execution after any previously launched jobs
sharing the same job name and user have terminated.
.RE
.TP
.TP
\fB\-D\fR, \fB\-\-chdir\fR=<\fIpath\fR>
\fB\-D\fR, \fB\-\-chdir\fR=<\fIpath\fR>
have the remote processes do a chdir to \fIpath\fR before beginning
have the remote processes do a chdir to \fIpath\fR before beginning
execution. The default is to chdir to the current working directory
execution. The default is to chdir to the current working directory
of the \fBsrun\fR process.
of the \fBsrun\fR process.
.TP
\fB\-d\fR, \fB\-\-slurmd\-debug\fR=<\fIlevel\fR>
Specify a debug level for slurmd(8). \fIlevel\fR may be an integer value
between 0 [quiet, only errors are displayed] and 4 [verbose operation].
The slurmd debug information is copied onto the stderr of
the job. By default only errors are displayed.
.TP
.TP
\fB\-e\fR, \fB\-\-error\fR=<\fImode\fR>
\fB\-e\fR, \fB\-\-error\fR=<\fImode\fR>
Specify how stderr is to be redirected. By default in interactive mode,
Specify how stderr is to be redirected. By default in interactive mode,
...
@@ -782,38 +807,6 @@ Open the output and error files using append or truncate mode as specified.
...
@@ -782,38 +807,6 @@ Open the output and error files using append or truncate mode as specified.
The default value is specified by the system configuration parameter
The default value is specified by the system configuration parameter
\fIJobFileAppend\fR.
\fIJobFileAppend\fR.
.TP
\fB\-P\fR, \fB\-\-dependency\fR=<\fIdependency_list\fR>
Defer the start of this job until the specified dependencies have been
satisfied completed.
<\fIdependency_list\fR> is of the form
<\fItype:job_id[:job_id][,type:job_id[:job_id]]\fR>.
Many jobs can share the same dependency and these jobs may even belong to
different users. The value may be changed after job submission using the
scontrol command.
.PD
.RS
.TP
\fBafter:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have begun
execution.
.TP
\fBafterany:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated.
.TP
\fBafternotok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have terminated
in some failed state (non-zero exit code, node failure, timed out, etc).
.TP
\fBafterok:job_id[:jobid...]\fR
This job can begin execution after the specified jobs have successfully
executed (ran to completion with non-zero exit code).
.TP
\fBsingleton\fR
This job can begin execution after any previously launched jobs sharing the same
job name and user have terminated.
.RE
.TP
.TP
\fB\-p\fR, \fB\-\-partition\fR=<\fIpartition name\fR>
\fB\-p\fR, \fB\-\-partition\fR=<\fIpartition name\fR>
Request a specific partition for the resource allocation. If not specified,
Request a specific partition for the resource allocation. If not specified,
...
@@ -944,6 +937,13 @@ By default, no signal is sent before the job's end time.
...
@@ -944,6 +937,13 @@ By default, no signal is sent before the job's end time.
If a \fIsig_num\fR is specified without any \fIsig_time\fR,
If a \fIsig_num\fR is specified without any \fIsig_time\fR,
the default time will be 60 seconds.
the default time will be 60 seconds.
.TP
\fB\-\-slurmd\-debug\fR=<\fIlevel\fR>
Specify a debug level for slurmd(8). \fIlevel\fR may be an integer
value between 0 [quiet, only errors are displayed] and 4 [verbose
operation]. The slurmd debug information is copied onto the stderr of
the job. By default only errors are displayed.
.TP
.TP
\fB\-T\fR, \fB\-\-threads\fR=<\fInthreads\fR>
\fB\-T\fR, \fB\-\-threads\fR=<\fInthreads\fR>
Request that \fBsrun\fR
Request that \fBsrun\fR
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment