holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Fix 'start' with AUTOMAKE=Yes

Browse Source
This commit is contained in:
Tom Eastep 2009-05-09 10:00:33 -07:00
parent c9538bbdee
commit be9573d30f
3 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -25,6 +25,8 @@ Changes in Shorewall 4.3.10
9) Implement nested HTB classes. 9) Implement nested HTB classes.
10) Fix 'start' with AUTOMAKE=Yes
Changes in Shorewall 4.3.9 Changes in Shorewall 4.3.9
1) Logging rules now create separate chain. 1) Logging rules now create separate chain.

6
Shorewall/releasenotes.txt
View File

@ -84,7 +84,11 @@ released late in 2009.
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
1. Previously, specifying a source port for SCTP in 1. Previously, specifying a source port for SCTP in
/etc/shorewall/tcfilters would cause an invalid rule to be generated. /etc/shorewall/tcfilters would cause an invalid rule to be
generated.
2. When AUTOMAKE=Yes, the 'shorewall start' ('shorewall6 start')
command used the wrong compiled script to start the firewall.
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
K N O W N P R O B L E M S R E M A I N I N G K N O W N P R O B L E M S R E M A I N I N G
---------------------------------------------------------------------------- ----------------------------------------------------------------------------

2
Shorewall/shorewall
View File

@ -480,7 +480,7 @@ start_command() {
if [ -n "$AUTOMAKE" ]; then if [ -n "$AUTOMAKE" ]; then
[ -n "$nolock" ] || mutex_on [ -n "$nolock" ] || mutex_on
${VARDIR}/.start $debugging start ${VARDIR}/firewall $debugging start
rc=$? rc=$?
[ -n "$nolock" ] || mutex_off [ -n "$nolock" ] || mutex_off
else else