From 965cc557853d2a1e4876765d61cccbda6213cdd5 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Fri, 16 Feb 2007 17:43:05 +0000
Subject: [PATCH] Clarify shell variable usage in 'stop' and 'stopped' scripts

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5415 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 docs/shorewall_extension_scripts.xml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/shorewall_extension_scripts.xml b/docs/shorewall_extension_scripts.xml
index 4ca130d79..3565cc8db 100644
--- a/docs/shorewall_extension_scripts.xml
+++ b/docs/shorewall_extension_scripts.xml
@@ -302,8 +302,12 @@
         <filename>shorewall.conf</filename>. So shell variables set in that
         file may be used in Shorewall configuration files only. Any variables
         that your extension scripts require at run-time on the firewall system
-        should be set in the <filename>init</filename> extension
-        script.</para>
+        should be set in the <filename>init</filename> extension script (if
+        you need variable values in the <filename>stop</filename> or
+        <filename>stopped</filename> scripts, you will need to set their value
+        in <filename>stop</filename> since <filename>init</filename> is not
+        invoked when processing the <command>stop</command> and
+        <command>clear</command> commands).</para>
 
         <para>When EXPORTPARAMS=Yes (the default), the
         <filename>/etc/shorewall/params</filename> script is processed during