From: Brendan O'Dea <bod@optus.net>
Date: Sun, 12 Jun 2005 05:54:39 +0000 (+0000)
Subject: clarify usage of shutdown signals
X-Git-Tag: 2.2.1-2fdn3.1~19^2^2~1^2~161
X-Git-Url: http://git.sameswireless.fr/l2tpns.git/commitdiff_plain/5282d5ccbd064db26dab99e65e4f521a8a8bbf7e?ds=inline

clarify usage of shutdown signals
---

diff --git a/Docs/manual.html b/Docs/manual.html
index a857d9b..ff7f0b3 100644
--- a/Docs/manual.html
+++ b/Docs/manual.html
@@ -696,12 +696,14 @@ killall -HUP l2tpns
 </PRE>
 
 The signals understood are:
-<UL>
-<LI>SIGHUP - Reload the config from disk and re-open log file</LI>
-<LI>SIGTERM / SIGINT - Shut down.</LI>
-<LI>SIGQUIT - Shut down cleanly.  This will send a disconnect message for
-every active session and tunnel before shutting down.</LI>
-</UL>
+<DL>
+<DT>SIGHUP</DT><DD>Reload the config from disk and re-open log file.</DD>
+<DT>SIGTERM, SIGINT</DT><DD>Stop process.  Tunnels and sessions are not
+terminated.  This signal should be used to stop l2tpns on a
+<A HREF="#Clustering">cluster node</A> where there are other machines to
+continue handling traffic.</DD>
+<DT>SIGQUIT</DT><DD>Shut down: closes sessions and tunnels.</DD>
+</DL>
 
 <H2 ID="Throttling">Throttling</H2>