extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-30 03:23:47 +01:00
Code Issues Packages Projects Releases Wiki Activity

Restore log messages

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3488 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-02-15 15:43:32 +00:00
parent 231845e6d9
commit 2f5eb26fcd
3 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -78,3 +78,5 @@ Changes in 3.1.x.
34) Correct Makefile. 34) Correct Makefile.
35) Add -t option 35) Add -t option
36) Restore log messages.

12
Shorewall/compiler
View File

@ -8665,6 +8665,18 @@ __EOF__
cp -f \$(my_pathname) /var/lib/shorewall/.restore cp -f \$(my_pathname) /var/lib/shorewall/.restore
case \$COMMAND in
start)
logger "Shorewall started"
;;
restart)
logger "Shorewall restarted"
;;
restore)
logger "Shorewall restored"
;;
esac
} }
# #

15
Shorewall/releasenotes.txt
View File

@ -37,11 +37,26 @@ Problems Corrected in 3.1.6
a re-compilation always occured even if the restore file was a re-compilation always occured even if the restore file was
current. current.
3) Log messages for "started", "restarted" and "restored" are once again
generated.
Other changes in 3.1.7 Other changes in 3.1.7
1) 'tcpsyn' has been changed to 'tcp:syn' (tcpsyn was added in 3.1.6). 1) 'tcpsyn' has been changed to 'tcp:syn' (tcpsyn was added in 3.1.6).
This new syntax is easier to extend in the future than was the old. This new syntax is easier to extend in the future than was the old.
2) /sbin/shorewall now supports a "-t" option that causes all progress
messages to be timestamped.
Example (VERBOSITY=0 in shorewall.conf):
gateway:/etc/shorewall # shorewall -t restart
07:08:51 Compiling...
07:09:05 Shorewall configuration compiled to /var/lib/shorewall/.restart
07:09:05 Restarting Shorewall....
07:09:08 done.
gateway:/etc/shorewall #
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: