summaryrefslogtreecommitdiff
path: root/bin/bbackupd
diff options
context:
space:
mode:
authorChris Wilson <chris+github@qwirx.com>2007-09-07 20:07:42 +0000
committerChris Wilson <chris+github@qwirx.com>2007-09-07 20:07:42 +0000
commit85e0afebafedb7852876571dfa3a8d1abad7de00 (patch)
tree587a0a7581f365665b0bc48626df60eae56b2341 /bin/bbackupd
parentf3e20f4376f6659f2db503a7861550a3ba7b814e (diff)
Document and enable KeepAliveTime option by default.
Diffstat (limited to 'bin/bbackupd')
-rwxr-xr-xbin/bbackupd/bbackupd-config.in19
1 files changed, 19 insertions, 0 deletions
diff --git a/bin/bbackupd/bbackupd-config.in b/bin/bbackupd/bbackupd-config.in
index 5dbd2dd9..b5dc8be8 100755
--- a/bin/bbackupd/bbackupd-config.in
+++ b/bin/bbackupd/bbackupd-config.in
@@ -341,6 +341,25 @@ MinimumFileAge = 21600
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