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

Don't tie EXPORTPARAMS to -e

Browse Source 
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/CompiledPrograms.xml
View File

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

5
docs/configuration_file_basics.xml
View File

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

35
docs/shorewall_extension_scripts.xml
View File

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