extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-22 06:10:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Document new try semantics in the Documentation

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5044 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-12-03 19:07:35 +00:00
parent 16f3b11b84
commit d1807d4e65
1 changed files with 27 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/starting_and_stopping_shorewall.xml
View File

@ -1342,7 +1342,7 @@ gateway:~ #</programlisting>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term>try (Deprecated - Not supported by Shorewall Lite)</term> <term>try (Not supported by Shorewall Lite)</term>
<listitem> <listitem>
<para><command>shorewall try &lt;configuration-directory&gt; [ <para><command>shorewall try &lt;configuration-directory&gt; [
@ -1360,8 +1360,9 @@ gateway:~ #</programlisting>
url="Documentation.htm#Conf">/etc/shorewall/shorewall.conf</ulink>) url="Documentation.htm#Conf">/etc/shorewall/shorewall.conf</ulink>)
exists. then that script is used.</para> exists. then that script is used.</para>
<para>The <command>try</command> command is deprecated. A better <para>The <command>try</command> command is deprecated in Shorewall
approach to testing new configurations is:</para> 3.0 and 3.2. A better approach to testing new configurations
is:</para>
<blockquote> <blockquote>
<para><command>shorewall save</command></para> <para><command>shorewall save</command></para>
@ -1382,6 +1383,29 @@ gateway:~ #</programlisting>
<para>…</para> <para>…</para>
</blockquote> </blockquote>
<para>Beginning with Shorewall version 3.3.6, the
<command>try</command> command has new and improved semantics as
follows:</para>
<blockquote>
<para>If Shorewall is started then the firewall state is saved to
a temporary saved configuration
(<filename>/var/lib/shorewall/.try</filename>). Next, if Shorewall
is currently started then a <command>restart</command> command is
issued; otherwise, a <command>start</command> command is
performed. if an error occurs during the compliation phase of the
<command>restart</command> or <command>start</command>, the
command terminates without changing the Shorewall state. If an
error occurs during the <command>restart</command> phase, then a
shorewall restore is performed using the saved configuration. If
an error occurs during the <command>start</command> phase, then
Shorewall is cleared. If the start/restart succeeds and a
&lt;<emphasis>timeout</emphasis>&gt; is specified then a
<command>clear</command> or <command>restore</command> is
performed after &lt;<emphasis>timeout</emphasis>&gt;
seconds.</para>
</blockquote>
</listitem> </listitem>
</varlistentry> </varlistentry>