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
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
b952d601
Commit
b952d601
authored
Jun 23, 2004
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Expand description of InactiveLimit.
parent
39af9fc7
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/man/man5/slurm.conf.5
+7
-4
7 additions, 4 deletions
doc/man/man5/slurm.conf.5
with
7 additions
and
4 deletions
doc/man/man5/slurm.conf.5
+
7
−
4
View file @
b952d601
.TH "slurm.conf" "5" "
May
2004" "Morris Jette" "Slurm configuration file"
.TH "slurm.conf" "5" "
June
2004" "Morris Jette" "Slurm configuration file"
.SH "NAME"
slurm.conf \- Slurm configuration file
.SH "DESCRIPTION"
...
...
@@ -108,10 +108,13 @@ The interval, in seconds, a job or job step is permitted to be inactive
before it is terminated. A job or job step is considered inactive if
the associated srun command is not responding to slurm daemons. This
could be due to the termination of the srun command or the program
being is a stopped state. This limit permits defunct jobs to be purged
in a timely fashion without waiting for their time limit to be reached.
being is a stopped state. A batch job is considered inactive if it
has no active job steps (e.g. periods of pre- and post-processing).
This limit permits defunct jobs to be purged in a timely fashion
without waiting for their time limit to be reached.
This value should reflect the possibility that the srun command may
stopped a debugger. The default value is unlimited (zero).
stopped by a debugger or considerable time could be required for batch
job pre- and post-processing. The default value is unlimited (zero).
.TP
\fBJobCompLoc\fR
Define the location where job completion records are to be logged.
...
...
...
...
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
sign in
to comment