Module: check_mk
Branch: master
Commit: da48b17bc764af50c2e50bcadd0653591515e7d6
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=da48b17bc764af…
Author: Andreas Umbreit <au(a)mathias-kettner.de>
Date: Mon Feb 18 16:33:06 2019 +0100
CMK-1544: Make the meaning of the timeout constant clearer
Change-Id: I03ba5b0e5623596deec428b9b697c1de1573082d
---
.werks/7164 | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/.werks/7164 b/.werks/7164
index be88e4c..4f950ed 100644
--- a/.werks/7164
+++ b/.werks/7164
@@ -15,9 +15,11 @@ This was particularly noticeable when running the agent updater under
Windows,
because the agent updater would fail to start over again, showing an error
like <code>copying plugins\cmk-update-agent.exe to temp\cmk-update-agent.exe
failed</code>.
-The agent updater now will cancel the connection if there is a connection timeout
detected
+The agent updater now will cancel the connection if it freezes.<br>
or if the connection freezes. The timeout limit is set to 120 seconds.<br>
-This timeout handling does not limit the overall connection time.
+This timeout handling does not limit the overall connection time.<br>
+For a detailled explenation have a look at the <i>Timeouts</i> paragraph at
the
+<a href="http://docs.python-requests.org">requests
documentation</a>!
Please note: This timeout is only active for connections handled by
python-requests.<br>
This fix won't apply if you are running the agent updater using cURL.