forked from extern/shorewall_code
Document new 'try' semantics in the release notes
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5043 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
e7dade4145
commit
16f3b11b84
@ -76,9 +76,23 @@ Other Changes in 3.3.6
|
|||||||
configuration once in the event of a failure. Previously, if there
|
configuration once in the event of a failure. Previously, if there
|
||||||
was a current 'safe' command in effect, then that configuration
|
was a current 'safe' command in effect, then that configuration
|
||||||
would be restored on a failure and then the last-running
|
would be restored on a failure and then the last-running
|
||||||
configuration would be restored.
|
configuration would be restored.
|
||||||
|
|
||||||
6) The syntax of the 'export' command has been made slightly
|
6) The 'try' command has been reimplemented with new semantics.
|
||||||
|
|
||||||
|
If Shorewall is started then the firewall state is saved to a
|
||||||
|
temporary saved configuration (/var/lib/shorewall/.try). Next, if
|
||||||
|
Shorewall is currently started then a restart command is issued;
|
||||||
|
otherwise, a start command is performed. if an error occurs during
|
||||||
|
the compliation phase of the restart or start, the command
|
||||||
|
terminates without changing the Shorewall state. If an error occurs
|
||||||
|
during the restart phase, then a 'shorewall restore' is performed
|
||||||
|
using the saved configuration. If an error occurs during the start
|
||||||
|
phase, then Shorewall is cleared. If the start/restart succeeds
|
||||||
|
and a timeout is specified then a 'clear' or 'restore' is performed
|
||||||
|
after timeout seconds.
|
||||||
|
|
||||||
|
7) The syntax of the 'export' command has been made slightly
|
||||||
friendlier.
|
friendlier.
|
||||||
|
|
||||||
The old syntax:
|
The old syntax:
|
||||||
|
Loading…
Reference in New Issue
Block a user