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
c9a82a78
Commit
c9a82a78
authored
20 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Make note of node ordering and its use in assigning a job step's tasks.
parent
183367ac
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/man5/slurm.conf.5
+3
-0
3 additions, 0 deletions
doc/man/man5/slurm.conf.5
with
3 additions
and
0 deletions
doc/man/man5/slurm.conf.5
+
3
−
0
View file @
c9a82a78
...
...
@@ -362,6 +362,9 @@ file only its "State" and "Reason" fields may be reset.
This may be useful to record the state of nodes which are temporarily
in a DOWN or DRAINED state without altering permanent configuration
information as shown in the example.
A job step's tasks are allocated to nodes in order the nodes appear
in the configuration file. There is presently no capability within
SLURM to arbitarily order a job step's tasks.
The node configuration specifies the following information:
.TP
\fBNodeName\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