extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-23 16:13:18 +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@5386 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-02-09 17:57:56 +00:00
parent 9daeaefc39
commit d01fbf61a3
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/compiler
View File

@ -5092,7 +5092,7 @@ __EOF__
__EOF__ __EOF__
fi fi
[ -n "$EXPORTPARAMS" -o -z "$EXPORT" ] && append_file params [ -n "$EXPORTPARAMS" ] && append_file params
cat >&3 << __EOF__ cat >&3 << __EOF__

3
Shorewall/releasenotes.txt
View File

@ -38,8 +38,7 @@ Problems Corrected in 3.4.0 RC2
than constant values such that it works correctly with Shorewall than constant values such that it works correctly with Shorewall
Lite. To work around this problem, a new EXPORTPARAMS option Lite. To work around this problem, a new EXPORTPARAMS option
has been added to shorewall.conf. When EXPORTPARAMS=No, the has been added to shorewall.conf. When EXPORTPARAMS=No, the
'params' file is no longer copied to the compiler output when the 'params' file is no longer copied to the compiler output.
'-e' flag is present.
With EXPORTPARAMS=No, uf you need to set environmental variables on With EXPORTPARAMS=No, uf you need to set environmental variables on
the firewall system for use by your extension scripts, then do so the firewall system for use by your extension scripts, then do so