When OpenSM is suspended by SIGSTOP it can miss subnet changes. Example
of known scenario is when another Stanby SM becomes master due to
unresponsive suspended master SM, when suspended SM continues to run
(after SIGCONT) we have two master SMs in a subnet.
To fix this we will schedule heavy sweep when SIGCONT is received.
Signed-off-by: Sasha Khapyorsky <[EMAIL PROTECTED]>
---
opensm/opensm/main.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/opensm/opensm/main.c b/opensm/opensm/main.c
index fe4262b..53648d6 100644
--- a/opensm/opensm/main.c
+++ b/opensm/opensm/main.c
@@ -111,6 +111,7 @@ static void setup_signals()
sigaction(SIGTERM, &act, NULL);
act.sa_handler = mark_hup_flag;
sigaction(SIGHUP, &act, NULL);
+ sigaction(SIGCONT, &act, NULL);
#ifndef HAVE_OLD_LINUX_THREADS
act.sa_handler = mark_usr1_flag;
sigaction(SIGUSR1, &act, NULL);
--
1.6.0.3.517.g759a
_______________________________________________
general mailing list
general@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
