From eb3dd7b3464251b0d58afadb7cf49c75e4ec6d1f Mon Sep 17 00:00:00 2001
From: Morris Jette <jette@schedmd.com>
Date: Fri, 10 Oct 2014 15:52:09 -0700
Subject: [PATCH] Note when setting node state power up/down happens

The power up/down request only takes effect after the ResumeTimeout
or SuspendTimeout is reached in order to avoid a race condition.
---
 doc/man/man1/scontrol.1 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/man/man1/scontrol.1 b/doc/man/man1/scontrol.1
index 4cf8980aeb8..0217cede7df 100644
--- a/doc/man/man1/scontrol.1
+++ b/doc/man/man1/scontrol.1
@@ -936,7 +936,9 @@ Setting a node "DOWN" will cause all running and suspended jobs on that
 node to be terminated.
 "POWER_DOWN" and "POWER_UP" will use the configured \fISuspendProg\fR and
 \fIResumeProg\fR programs to explicitly place a node in or out of a power
-saving mode.
+saving mode. If a node is already in the process of being powered up or down,
+the command will have no effect until the configured ResumeTimeout or
+SuspendTimeout is reached.
 The "NoResp" state will only set the "NoResp" flag for a node without
 changing its underlying state.
 While all of the above states are valid, some of them are not valid new
-- 
GitLab