From 9dcf28d7ff24513ff5b049a1057ddb9231b093a5 Mon Sep 17 00:00:00 2001
From: Moe Jette <jette1@llnl.gov>
Date: Wed, 30 Jul 2003 20:13:09 +0000
Subject: [PATCH] Clarify resetting a node's state and reason in the
 configuration file.

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

diff --git a/doc/man/man5/slurm.conf.5 b/doc/man/man5/slurm.conf.5
index 7e6daa0a84f..872e33855d0 100644
--- a/doc/man/man5/slurm.conf.5
+++ b/doc/man/man5/slurm.conf.5
@@ -265,6 +265,11 @@ of larger clusters.
 In order to support the concept of jobs requiring consecutive nodes
 on some architectures, 
 node specifications should be place in this file in consecutive order.
+If a specific node name is listed more than once in the configuration 
+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.
 The node configuration specifies the following information: 
 .TP
 \fBNodeName\fR
@@ -507,7 +512,9 @@ NodeName=DEFAULT State=UNKNOWN
 .br
 NodeName=dev[0-25] NodeAddr=edev[0-25] Weight=16
 .br
-NodeName=dev26 State=DOWN Reason="power,ETA=Dec25"
+# Update records for specific DOWN nodes
+.br
+NodeName=dev20 State=DOWN Reason="power,ETA=Dec25"
 .br
 #
 .br
-- 
GitLab