[Box Backup-commit] COMMIT r1816 - box/chris/merge/bin/bbackupd
boxbackup-dev@fluffy.co.uk
boxbackup-dev@fluffy.co.uk
Fri, 07 Sep 2007 21:07:43 +0100
Author: chris
Date: 2007-09-07 21:07:42 +0100 (Fri, 07 Sep 2007)
New Revision: 1816
Modified:
box/chris/merge/bin/bbackupd/bbackupd-config.in
Log:
Document and enable KeepAliveTime option by default.
Modified: box/chris/merge/bin/bbackupd/bbackupd-config.in
===================================================================
--- box/chris/merge/bin/bbackupd/bbackupd-config.in 2007-09-06 23:10:10 UTC (rev 1815)
+++ box/chris/merge/bin/bbackupd/bbackupd-config.in 2007-09-07 20:07:42 UTC (rev 1816)
@@ -341,6 +341,25 @@
MaxUploadWait = 86400
+# If the connection is idle for some time (e.g. over 10 minutes or 600
+# seconds, not sure exactly how long) then the server will give up and
+# disconnect the client, resulting in Connection Protocol_Timeout errors
+# on the server and TLSReadFailed or TLSWriteFailed errors on the client.
+# Also, some firewalls and NAT gateways will kill idle connections after
+# similar lengths of time.
+#
+# This can happen for example when most files are backed up already and
+# don't need to be sent to the store again, while scanning a large
+# directory, or while calculating diffs of a large file. To avoid this,
+# KeepAliveTime specifies that special keep-alive messages should be sent
+# when the connection is otherwise idle for a certain length of time,
+# specified here in seconds.
+#
+# The default is that these messages are never sent, equivalent to setting
+# this option to zero, but we recommend that all users enable this.
+
+KeepAliveTime = 120
+
__E
}
else