|
 |
b833e0 |
From 171b664ec4a7c94583b35597bd7e1e72bf89d217 Mon Sep 17 00:00:00 2001
|
|
|
b833e0 |
From: =?UTF-8?q?Pawe=C5=82=20Po=C5=82awski?= <ppolawsk@redhat.com>
|
|
|
b833e0 |
Date: Wed, 2 Dec 2020 03:10:50 +0100
|
|
|
b833e0 |
Subject: [PATCH 18/18] data_provider_be: MAN page update
|
|
|
b833e0 |
|
|
|
b833e0 |
Updated description of parameters:
|
|
|
b833e0 |
* offline_timeout
|
|
|
b833e0 |
* offline_timeout_max
|
|
|
b833e0 |
|
|
|
b833e0 |
MAN page now explains that in some circumstances
|
|
|
b833e0 |
corelation of offline_timeout and offline_timeout_max values
|
|
|
b833e0 |
may lead to offline checking interval not incrementing.
|
|
|
b833e0 |
This is a false positive error as in fact the value
|
|
|
b833e0 |
just saturates almost instantly.
|
|
|
b833e0 |
|
|
|
b833e0 |
Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com>
|
|
|
b833e0 |
---
|
|
|
b833e0 |
src/man/sssd.conf.5.xml | 14 ++++++++++++--
|
|
|
b833e0 |
1 file changed, 12 insertions(+), 2 deletions(-)
|
|
|
b833e0 |
|
|
|
b833e0 |
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml
|
|
|
b833e0 |
index d637e2eaa..8b330de58 100644
|
|
|
b833e0 |
--- a/src/man/sssd.conf.5.xml
|
|
|
b833e0 |
+++ b/src/man/sssd.conf.5.xml
|
|
|
b833e0 |
@@ -739,12 +739,12 @@
|
|
|
b833e0 |
offline_timeout + random_offset
|
|
|
b833e0 |
</para>
|
|
|
b833e0 |
<para>
|
|
|
b833e0 |
- The random offset can increment up to 30 seconds.
|
|
|
b833e0 |
+ The random offset value is from 0 to 30.
|
|
|
b833e0 |
After each unsuccessful attempt to go online,
|
|
|
b833e0 |
the new interval is recalculated by the following:
|
|
|
b833e0 |
</para>
|
|
|
b833e0 |
<para>
|
|
|
b833e0 |
- new_interval = old_interval*2 + random_offset
|
|
|
b833e0 |
+ new_interval = (old_interval * 2) + random_offset
|
|
|
b833e0 |
</para>
|
|
|
b833e0 |
<para>
|
|
|
b833e0 |
Note that the maximum length of each interval
|
|
|
b833e0 |
@@ -769,6 +769,16 @@
|
|
|
b833e0 |
<para>
|
|
|
b833e0 |
A value of 0 disables the incrementing behaviour.
|
|
|
b833e0 |
</para>
|
|
|
b833e0 |
+ <para>
|
|
|
b833e0 |
+ The value of this parameter should be set in correlation
|
|
|
b833e0 |
+ to offline_timeout parameter value.
|
|
|
b833e0 |
+ </para>
|
|
|
b833e0 |
+ <para>
|
|
|
b833e0 |
+ With offline_timeout set to 60 (default value) there is no point
|
|
|
b833e0 |
+ in setting offlinet_timeout_max to less than 120 as it will
|
|
|
b833e0 |
+ saturate instantly. General rule here should be to set
|
|
|
b833e0 |
+ offline_timeout_max to at least 4 times offline_timeout.
|
|
|
b833e0 |
+ </para>
|
|
|
b833e0 |
<para>
|
|
|
b833e0 |
Although a value between 0 and offline_timeout may be
|
|
|
b833e0 |
specified, it has the effect of overriding the
|
|
|
b833e0 |
--
|
|
|
b833e0 |
2.21.3
|
|
|
b833e0 |
|