From c9a82a7880c2398135552269f9fde50b43a42da0 Mon Sep 17 00:00:00 2001
From: Moe Jette <jette1@llnl.gov>
Date: Wed, 18 Aug 2004 01:20:45 +0000
Subject: [PATCH] Make note of node ordering and its use in assigning a job
 step's tasks.

---
 doc/man/man5/slurm.conf.5 | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/man/man5/slurm.conf.5 b/doc/man/man5/slurm.conf.5
index 2da94ce898f..dc61cb71c7e 100644
--- a/doc/man/man5/slurm.conf.5
+++ b/doc/man/man5/slurm.conf.5
@@ -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
-- 
GitLab