extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-22 05:28:59 +01:00
Code Issues Packages Projects Releases Wiki Activity

Remove SUBSYSLOCK code from default and debian footers

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3663 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-03-12 22:18:00 +00:00
parent e1fbd64cdd
commit f03167870a
4 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -2,6 +2,8 @@ Changes in 3.2.0 Beta 2
1) Make "shorewall start -f" work correctly. 1) Make "shorewall start -f" work correctly.
2) Remove SUBSYSLOCK code from default and debian footers.
Changes in 3.1.x. and 3.2.x Changes in 3.1.x. and 3.2.x
1) Removal of dynamic zones. 1) Removal of dynamic zones.

1
Shorewall/prog.footer
View File

@ -91,7 +91,6 @@ case "$COMMAND" in
progress_message3 "Clearing Shorewall...." progress_message3 "Clearing Shorewall...."
clear_firewall clear_firewall
status=0 status=0
[ -n "$SUBSYSLOCK" ] && rm -f $SUBSYSLOCK
progress_message3 "done." progress_message3 "done."
;; ;;
status) status)

1
Shorewall/prog.footer.debian
View File

@ -91,7 +91,6 @@ case "$COMMAND" in
progress_message3 "Clearing Shorewall...." progress_message3 "Clearing Shorewall...."
clear_firewall clear_firewall
status=0 status=0
[ -n "$SUBSYSLOCK" ] && rm -f $SUBSYSLOCK
progress_message3 "done." progress_message3 "done."
;; ;;
status) status)

4
Shorewall/releasenotes.txt
View File

@ -34,6 +34,10 @@ Problems Corrected in 3.2.0 Beta 2
updated to define RESTOREFILE when it invokes 'make' during processing updated to define RESTOREFILE when it invokes 'make' during processing
of the "shorewall start -f" command. of the "shorewall start -f" command.
2) Code involving SUBSYSLOCK has been removed from the default and Debian
program footers. SUBSYSLOCK only applies to programs installed in
/etc/init.d/.
Migration Considerations: Migration Considerations:
1) A number of macros have been split into two. The macros affected are: 1) A number of macros have been split into two. The macros affected are: