1
0
mirror of https://gitlab.com/shorewall/code.git synced 2025-02-16 17:51:16 +01:00

Document MUTEX_TIMEOUT in release notes and change log

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@153 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2002-07-24 14:34:28 +00:00
parent 6e238a6e4e
commit 1c235e096d
3 changed files with 22 additions and 0 deletions

View File

@ -17,3 +17,5 @@ Changes since 1.3.4
7. Centralize the adding of IP aliases
8. Added MUTEX_TIMEOUT variable.

View File

@ -14,3 +14,20 @@ In this release:
3. The time that the counters were last reset is now displayed in the
heading of the 'status' and 'show' commands.
4. Added MUTEX_TIMEOUT variable in shorewall.conf and changed the way
in which Shorewall protects itself from concurrent state
changes.
Previously, if a state-changing operation (like restart)
found a lock file, it would wait for 30 seconds for the lock file to
be removed. If the file was not removed within 30 seconds, a message
was issued and the operation was aborted.
With the new code, the wait time is determined by the value of
MUTEX_TIMEOUT (default 60 seconds). If the file is not removed
within MUTEX_TIMEOUT, the state-changing operation will assume that
the lock file is stale and will issue a message and continue.
An appopriate setting for MUTEX_TIMEOUT is twice the time that it takes
your firewall system to process a "shorewall restart" command.

View File

@ -300,6 +300,9 @@ MERGE_HOSTS=Yes
# that the last program to hold the lock died without releasing the lock.
#
# If not set or set to the empty value, a value of 60 (60 seconds) is assumed.
#
# An appropriate value for this parameter would be twice the length of time
# that it takes your firewall system to process a "shorewall restart" command.
MUTEX_TIMEOUT=60