extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-21 02:08:48 +02:00
Code Issues Packages Projects Releases Wiki Activity

Clarify shell variable usage in 'stop' and 'stopped' scripts

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5415 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-02-16 17:43:05 +00:00
parent b157829bd1
commit 965cc55785
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/shorewall_extension_scripts.xml
View File

@ -302,8 +302,12 @@
<filename>shorewall.conf</filename>. So shell variables set in that <filename>shorewall.conf</filename>. So shell variables set in that
file may be used in Shorewall configuration files only. Any variables file may be used in Shorewall configuration files only. Any variables
that your extension scripts require at run-time on the firewall system that your extension scripts require at run-time on the firewall system
should be set in the <filename>init</filename> extension should be set in the <filename>init</filename> extension script (if
script.</para> 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 <para>When EXPORTPARAMS=Yes (the default), the
<filename>/etc/shorewall/params</filename> script is processed during <filename>/etc/shorewall/params</filename> script is processed during