Don't tie EXPORTPARAMS to -e

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5384 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-02-09 17:56:09 +00:00
parent 51bfeb027a
commit 350c16a922
3 changed files with 21 additions and 25 deletions

View File

@ -104,8 +104,7 @@
<listitem> <listitem>
<para>Beginning with Shorewall 3.2.9 and 3.4.0 RC2, the <para>Beginning with Shorewall 3.2.9 and 3.4.0 RC2, the
<filename>params</filename> file is only processed at compile <filename>params</filename> file is only processed at compile
time if the <link linkend="Compile">-e compiler option</link> is time if you set EXPORTPARAMS=No in
given and you set EXPORTPARAMS=No in
<filename>shorewall.conf</filename>. For run-time setting of <filename>shorewall.conf</filename>. For run-time setting of
shell variables, use the <filename>init</filename> extension shell variables, use the <filename>init</filename> extension
script. Although the default setting is EXPORTPARAMS=Yes for script. Although the default setting is EXPORTPARAMS=Yes for
@ -667,8 +666,7 @@ clean:
<listitem> <listitem>
<para>Beginning with Shorewall 3.2.9 and 3.4.0 RC2, the <para>Beginning with Shorewall 3.2.9 and 3.4.0 RC2, the
<filename>params</filename> file is only processed at compile <filename>params</filename> file is only processed at compile
time if the <link linkend="Compile">-e compiler option</link> is time if you set EXPORTPARAMS=No in
given and you set EXPORTPARAMS=No in
<filename>shorewall.conf</filename>. For run-time setting of <filename>shorewall.conf</filename>. For run-time setting of
shell variables, use the <filename>init</filename> extension shell variables, use the <filename>init</filename> extension
script.</para> script.</para>

View File

@ -729,9 +729,8 @@ DNAT net loc:192.168.1.3 tcp 4000:4100</programlisting>
<listitem> <listitem>
<para>The <filename>/etc/shorewall/params</filename> file is processed <para>The <filename>/etc/shorewall/params</filename> file is processed
by the compiler at compile-time and by the compiled script at by the compiler at compile-time and by the compiled script at
run-time. Beginning with Shorewall 3.2.9 and 3.4.0 RC2, if the "-e" run-time. Beginning with Shorewall 3.2.9 and 3.4.0 RC2, if you have
flag is given to the compiler and you have set EXPORTPARAMS=No in set EXPORTPARAMS=No in <filename>shorewall.conf</filename>, then the
<filename>shorewall.conf</filename>, then the
<filename><filename>params</filename></filename> file is only <filename><filename>params</filename></filename> file is only
processed by the compiler; it is not run by the compiled processed by the compiler; it is not run by the compiled
script.</para> script.</para>

View File

@ -298,25 +298,24 @@
<note> <note>
<para>The <filename>/etc/shorewall/params</filename> script is <para>The <filename>/etc/shorewall/params</filename> script is
processed only during compilation if the "-e" compiler flag is given processed only during compilation if EXPORTPARAMS=No in
and EXPORTPARAMS=No in <filename>shorewall.conf</filename>. So shell <filename>shorewall.conf</filename>. So shell variables set in that
variables set in that file may be used in Shorewall configuration file may be used in Shorewall configuration files only. Any variables
files only. Any variables that your extension scripts require at that your extension scripts require at run-time on the firewall system
run-time on the firewall system should be set in the should be set in the <filename>init</filename> extension
<filename>init</filename> extension script.</para> script.</para>
<para>When the "-e" flag is not given or when EXPORTPARAMS=Yes (the <para>When EXPORTPARAMS=Yes (the default), the
default), the <filename>/etc/shorewall/params</filename> script is <filename>/etc/shorewall/params</filename> script is processed during
processed during compilation <emphasis role="bold">and</emphasis> compilation <emphasis role="bold">and</emphasis> copied into the
copied into the compiled script as described above. So shell variables compiled script as described above. So shell variables set during
set during compilation may be used in Shorewall configuration files compilation may be used in Shorewall configuration files while those
while those set at run-time are available to your other extension set at run-time are available to your other extension scripts.Note
scripts.Note that if you assign dynamic values to variables, there is that if you assign dynamic values to variables, there is no guarantee
no guarantee that the value calculated at compile time will be the that the value calculated at compile time will be the same as what is
same as what is calculated at run time. This is particularly true if calculated at run time. This is particularly true if you use the
you use the <command>shorewall compile</command> command to compile a <command>shorewall compile</command> command to compile a program then
program then run that program at a later time or if you use Shorewall run that program at a later time or if you use Shorewall Lite.</para>
Lite.</para>
</note> </note>
<note> <note>