holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Fix indentation in manpage

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9437 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2009-02-12 15:44:12 +00:00
parent 1fbfdd77fc
commit bfc3b2d82b
1 changed files with 47 additions and 50 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

59
manpages/shorewall-rules.xml
View File

@ -435,36 +435,30 @@
separated by a slash (e.g. FTP/ACCEPT) is still allowed but is separated by a slash (e.g. FTP/ACCEPT) is still allowed but is
deprecated.</para> deprecated.</para>
<programlisting></programlisting> <para>The <emphasis role="bold">ACTION</emphasis> may
</listitem> optionally be followed by ":" and a syslog log level (e.g,
</varlistentry> REJECT:info or DNAT:debug). This causes the packet to be
</variablelist> logged at the specified level. Note that if the <emphasis
role="bold">ACTION</emphasis> involves destination network
<blockquote> address translation (DNAT, REDIRECT, SAME, etc.) then the
<para>The <emphasis role="bold">ACTION</emphasis> may optionally packet is logged <emphasis role="bold">before</emphasis> the
be followed by ":" and a syslog log level (e.g, REJECT:info or destination address is rewritten.</para>
DNAT:debug). This causes the packet to be logged at the specified
level. Note that if the <emphasis role="bold">ACTION</emphasis>
involves destination network address translation (DNAT, REDIRECT,
SAME, etc.) then the packet is logged <emphasis
role="bold">before</emphasis> the destination address is
rewritten.</para>
<para>If the <emphasis role="bold">ACTION</emphasis> names an <para>If the <emphasis role="bold">ACTION</emphasis> names an
<emphasis>action</emphasis> declared in <ulink <emphasis>action</emphasis> declared in <ulink
url="shorewall-actions.html">shorewall-actions</ulink>(5) or in url="shorewall-actions.html">shorewall-actions</ulink>(5) or
/usr/share/shorewall/actions.std then:</para> in /usr/share/shorewall/actions.std then:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>If the log level is followed by "!' then all rules in <para>If the log level is followed by "!' then all rules
the action are logged at the log level.</para> in the action are logged at the log level.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>If the log level is not followed by "!" then only those <para>If the log level is not followed by "!" then only
rules in the action that do not specify logging are logged at those rules in the action that do not specify logging are
the specified level.</para> logged at the specified level.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -474,20 +468,23 @@
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>You may also specify <emphasis role="bold">ULOG</emphasis> <para>You may also specify <emphasis
or <emphasis role="bold">NFLOG</emphasis> (must be in upper case) role="bold">ULOG</emphasis> or <emphasis
as a log level.This will log to the ULOG or NFLOG target for role="bold">NFLOG</emphasis> (must be in upper case) as a log
routing to a separate log through use of ulogd (<ulink level.This will log to the ULOG or NFLOG target for routing to
a separate log through use of ulogd (<ulink
url="http://www.netfilter.org/projects/ulogd/index.html">http://www.netfilter.org/projects/ulogd/index.html</ulink>).</para> url="http://www.netfilter.org/projects/ulogd/index.html">http://www.netfilter.org/projects/ulogd/index.html</ulink>).</para>
<para>Actions specifying logging may be followed by a log tag (a <para>Actions specifying logging may be followed by a log tag
string of alphanumeric characters) which is appended to the string (a string of alphanumeric characters) which is appended to the
generated by the LOGPREFIX (in <ulink string generated by the LOGPREFIX (in <ulink
url="shorewall.conf.html">shorewall.conf</ulink>(5)).</para> url="shorewall.conf.html">shorewall.conf</ulink>(5)).</para>
<para>Example: ACCEPT:info:ftp would include 'ftp ' at the end of <para>Example: ACCEPT:info:ftp would include 'ftp ' at the end
the log prefix generated by the LOGPREFIX setting.</para> of the log prefix generated by the LOGPREFIX setting.</para>
</blockquote> </listitem>
</varlistentry>
</variablelist>
</listitem> </listitem>
</varlistentry> </varlistentry>