New syntax convention in zones manpage

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4994 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-11-23 17:53:40 +00:00
parent 41ff9b3089
commit a2b2f90473

View File

@ -43,14 +43,17 @@
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term><emphasis role="bold">ZONE</emphasis></term> <term><emphasis role="bold">ZONE</emphasis>
<emphasis>zone</emphasis>[<emphasis
role="bold">:</emphasis><emphasis>parent-zone</emphasis>[<emphasis
role="bold">,</emphasis><emphasis>parent-zone</emphasis>]...]</term>
<listitem> <listitem>
<para>Short name of the zone. The names "all" and "none" are <para>Nname of the <emphasis>zone</emphasis>. The names "all" and
reserved and may not be used as zone names. The maximum length of a "none" are reserved and may not be used as zone names. The maximum
zone name is determined by the setting of the LOGFORMAT option in length of a zone name is determined by the setting of the LOGFORMAT
shorewall.conf. With the default LOGFORMAT, zone names can be at option in shorewall.conf. With the default LOGFORMAT, zone names can
most 5 characters long.</para> be at most 5 characters long.</para>
<para>Where a zone is nested in one or more other zones, you may <para>Where a zone is nested in one or more other zones, you may
follow the (sub)zone name by ":" and a comma-separated list of the follow the (sub)zone name by ":" and a comma-separated list of the
@ -118,7 +121,8 @@ c:a,b ipv4</programlisting>
<varlistentry> <varlistentry>
<term><emphasis role="bold">OPTIONS, IN OPTIONS and OUT <term><emphasis role="bold">OPTIONS, IN OPTIONS and OUT
OPTIONS</emphasis></term> OPTIONS</emphasis> — [<emphasis>option</emphasis>[<emphasis
role="bold">,</emphasis><emphasis>option</emphasis>]...]</term>
<listitem> <listitem>
<para>A comma-separated list of options.</para> <para>A comma-separated list of options.</para>