extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-22 23:53:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

Cosmetic cleanup of the .conf manpages

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2012-12-27 09:01:37 -08:00
parent 8bb6f81dc5
commit f96bc7cc2d
2 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Shorewall/manpages/shorewall.conf.xml
View File

@ -285,11 +285,12 @@
role="bold">Yes</emphasis>|<emphasis role="bold">No</emphasis>]</term>
<listitem>
<para>Added in Shorewall 4.5.12. When set to 'No' (the default), the
compiler issues a warning when it finds a capabilities file that
doesn't specify all of the capabilities supported by the compiler.
When IGNOREOLDCAPVERSIONS is set to 'Yes', no warning is
issued.</para>
<para>Added in Shorewall 4.5.12. When set to <emphasis
role="bold">No</emphasis> (the default), the compiler issues a
warning when it finds a capabilities file that doesn't specify all
of the capabilities supported by the compiler. When
IGNOREOLDCAPVERSIONS is set to <emphasis role="bold">Yes</emphasis>,
no warning is issued.</para>
</listitem>
</varlistentry>
@ -302,8 +303,9 @@
<para>Added in Shorewall 4.5.11. Normally, if an unknown shell
variable is encountered in a configuration file (except in ?IF and
?ELSIF directives), the compiler raises a fatal error. If
IGNOREUNKNOWNVARIABLES is set to 'Yes', then such variables simply
expand to an empty string. Default is 'No'.</para>
IGNOREUNKNOWNVARIABLES is set to <emphasis
role="bold">Yes</emphasis>, then such variables simply expand to an
empty string. Default is <emphasis role="bold">No</emphasis>.</para>
</listitem>
</varlistentry>

16
Shorewall6/manpages/shorewall6.conf.xml
View File

@ -222,11 +222,12 @@
role="bold">Yes</emphasis>|<emphasis role="bold">No</emphasis>]</term>
<listitem>
<para>Added in Shorewall 4.5.12. When set to 'No' (the default), the
compiler issues a warning when it finds a capabilities file that
doesn't specify all of the capabilities supported by the compiler.
When IGNOREOLDCAPVERSIONS is set to 'Yes', no warning is
issued.</para>
<para>Added in Shorewall 4.5.12. When set to <emphasis
role="bold">No</emphasis> (the default), the compiler issues a
warning when it finds a capabilities file that doesn't specify all
of the capabilities supported by the compiler. When
IGNOREOLDCAPVERSIONS is set to <emphasis role="bold">Yes</emphasis>,
no warning is issued.</para>
</listitem>
</varlistentry>
@ -239,8 +240,9 @@
<para>Added in Shorewall 4.5.11. Normally, if an unknown shell
variable is encountered in a configuration file (except in ?IF and
?ELSIF directives), the compiler raises a fatal error. If
IGNOREUNKNOWNVARIABLES is set to 'Yes', then such variables simply
expand to an empty string. Default is 'No'.</para>
IGNOREUNKNOWNVARIABLES is set to <emphasis
role="bold">Yes</emphasis>, then such variables simply expand to an
empty string. Default is <emphasis role="bold">No</emphasis>.</para>
</listitem>
</varlistentry>