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
b1de8124
Commit
b1de8124
authored
19 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Expand description of srun --no-kill option.
parent
d48e0f4f
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/man/man1/srun.1
+2
-0
2 additions, 0 deletions
doc/man/man1/srun.1
with
2 additions
and
0 deletions
doc/man/man1/srun.1
+
2
−
0
View file @
b1de8124
...
...
@@ -104,6 +104,8 @@ will block until resources become available.
\fB\-k\fR, \fB\-\-no-kill\fR
Do not automatically terminate a job of one of the nodes it has been allocated
fails. The job will assume all responsibilities for fault-tolerance. The
active job step (MPI job) will almost certainly suffer a fatal error,
but subsequent job steps may be run if this option is specified. The
default action is to terminate job upon node failure. Note that
\fB\-\-batch\fR jobs will be re-queued if a node failure occurs in the
process of initiating it.
...
...
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