extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-26 15:39:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Even more 3.2.0 Documentation Updates

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3894 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-05-07 15:58:26 +00:00
parent d31e897793
commit 011a07e367
4 changed files with 1233 additions and 9763 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/images/State_Diagram.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 18 KiB

10950
docs/images/State_Diagram.vdx
View File

File diff suppressed because one or more lines are too long

36
docs/starting_and_stopping_shorewall.xml
View File

@ -1147,16 +1147,16 @@
</section>
<section id="State">
<title>Shorewall State Diagram (Shorewall 3.0 and earlier)</title>
<title>Shorewall State Diagram</title>
<para>The Shorewall State Diargram is depicted below.</para>
<para><graphic align="center" fileref="images/State_Diagram.png" /></para>
<para>You will note that the commands that result in state transitions use
the word <quote>firewall</quote> rather than <quote>shorewall</quote>.
That is because the actual transitions are done by
<command>/usr/share/shorewall/firewall</command>;
<para>You will note that mose of the commands that result in state
transitions use the word <quote>firewall</quote> rather than
<quote>shorewall</quote>. That is because the actual transitions are done
by <command>/usr/share/shorewall/firewall</command>;
<command>/sbin/shorewall</command> runs <quote>firewall</quote> according
to the following table:</para>
@ -1258,5 +1258,31 @@
</tbody>
</tgroup>
</informaltable>
<para>The only time that a program other than
<command>/usr/share/shorewall/firewall</command> performs a state
transition itself is when it executes the <command>shorewall
restore</command> command is executed. In that case, the
<command>/var/lib/shorewall/restore</command> program sets the state to
"Started".</para>
<section>
<title>Notes for Shorewall 3.2.0 and Later</title>
<para>With any command that involves compilation, there is no state
transition while the compiler is running. If compilation fails, the
state remains unchanged.</para>
<para>Also, <command>shorewall start</command> and <command>shorewall
restart</command> involve compilation followed by execution of the
compiled script. So it is the compiled script that performs the state
transition in these commands rather than
<command>/usr/share/shorewall/firewall</command>.</para>
<para>The compiled script is placed in <filename
class="directory">/var/lib/shorewall</filename> and is named either
<filename>.start</filename> or <filename>.restart</filename> depending
on the command.</para>
</section>
</section>
</article>

10
docs/support.xml
View File

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>2006-04-20</pubdate>
<pubdate>2006-05-07</pubdate>
<copyright>
<year>2001-2006</year>
@ -122,6 +122,14 @@
<para>Forward the <filename>/tmp/trace</filename> file as an
attachment compressed with gzip or bzip2.</para>
<para>If you are running Shorewall version 3.2.0 or later and
compilation succeeds but the compiled program fails, then please
include the compiled program with your report. The compiled program
will be named <filename>/var/lib/shorewall/.start</filename> if the
command is <command>shorewall start</command> and it will be named
<filename>/var/lib/shorewall/.restart</filename> if the command is
<command>shorewall restart</command>.</para>
</blockquote>
</listitem>