From d5de93a9a6ddc9da484a13c115d1b4f5bc4777cc Mon Sep 17 00:00:00 2001
From: Moe Jette <jette1@llnl.gov>
Date: Fri, 21 Mar 2003 23:08:10 +0000
Subject: [PATCH] Describe what can be done with reconfig command.

---
 doc/man/man1/scontrol.1 | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/man/man1/scontrol.1 b/doc/man/man1/scontrol.1
index 7a7c1fec7ca..235f22f9487 100644
--- a/doc/man/man1/scontrol.1
+++ b/doc/man/man1/scontrol.1
@@ -58,12 +58,18 @@ Terminate the execution of scontrol.
 .TP
 \fIreconfigure\fP
 Instruct all Slurm daemons to re-read the configuration file. 
+This command does not restart the daemons.
 This mechanism would be used to modify configuration parameters (Epilog, 
 Prolog, SlurmctldLogFile, SlurmdLogFile, etc.) register the physical 
 addition or removal of nodes from the cluster or recognize the change 
 of a node's configuration, such as the addition of memory or processors. 
 The Slurm controller (slurmctld) forwards the request all other daemons 
 (slurmd daemon on each compute node). Running jobs continue execution.
+Most configuration parameters can be changed by just running this command, 
+however, SLURM daemons should be shutdown and restarted if any of these 
+parameters are to be changed: AuthType, BackupAddr, BackupController, 
+ControlAddr, ControlMach, PluginDir, StateSaveLocation, SlurmctldPort 
+or SlurmdPort.
 .TP
 \fIshow\fP \fIENTITY\fP \fIID\fP
 Display the state of the specified entity with the specified identification.
-- 
GitLab