dont set some of the sysctl variables in statd-callout. these are

mainly useful for avoiding ack-storms when doing very rapid
failover/failback during testing   but should not be required in
real-world.

this gets rid of a lof of annoying messages from the messages file

(This used to be ctdb commit 50d289dcce2caa7c7be9b6faa3b38b69c2237038)

diff --git a/ctdb/config/statd-callout b/ctdb/config/statd-callout
index f582a1a8e028358b3c88cef833d43dad5db48770..7709df411b0230dd8c49d691c384b2f49413b4ce 100755 (executable)
--- a/ctdb/config/statd-callout
+++ b/ctdb/config/statd-callout
@@ -50,9 +50,9 @@ case "$1" in
 
        # we need these settings to make sure that no tcp connections survive
        # across a very fast failover/failback
-       echo 0 > /proc/sys/net/ipv4/tcp_max_tw_buckets
-       echo 0 > /proc/sys/net/ipv4/tcp_fin_timeout
-       echo 0 > /proc/sys/net/ipv4/tcp_max_orphans
+       echo 10 > /proc/sys/net/ipv4/tcp_fin_timeout
+       #echo 0 > /proc/sys/net/ipv4/tcp_max_tw_buckets
+       #echo 0 > /proc/sys/net/ipv4/tcp_max_orphans
 
        # rebuild the state directory for the local statd to use the correct
        # state value and to initally send notifications to all clients