From 16025c3abb3a921888b1d7b709700c57213761ac Mon Sep 17 00:00:00 2001
From: Moe Jette <jette1@llnl.gov>
Date: Fri, 5 May 2006 19:46:30 +0000
Subject: [PATCH] No changes to logic, just modifiy comments for greater
 clarity.

---
 src/slurmctld/controller.c | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/slurmctld/controller.c b/src/slurmctld/controller.c
index 83b2c323efa..872f4cd256b 100644
--- a/src/slurmctld/controller.c
+++ b/src/slurmctld/controller.c
@@ -90,15 +90,18 @@
  * To test for memory leaks, set MEM_LEAK_TEST to 1 then execute
  * > valgrind --tool=memcheck --leak-check=yes --num-callers=6 
  *    --leak-resolution=med slurmctld -D
- * then exercise the slurmctld functionality before executing
+ *
+ * Then exercise the slurmctld functionality before executing
  * > scontrol shutdown
  *
  * The OpenSSL code produces a bunch of errors related to use of 
- * non-initialized memory use. 
+ *    non-initialized memory use. 
  * The switch/elan plugin orphans 640 bytes at shutdown.
+ * The list functions will report memory "possibly lost". The memory is 
+ *    used for a cache, which is really OK.
  * Otherwise the report should be free of errors. Remember to reset 
- * MEM_LEAK_TEST to 0 afterwards for best system response (non-seamless 
- * backup controller use).
+ *    MEM_LEAK_TEST to 0 afterwards for best system response (non-seamless 
+ *    backup controller use).
 \**************************************************************************/
 #define MEM_LEAK_TEST     0	/* Running memory leak test if set */
 
-- 
GitLab