summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichal Zidek <mzidek@redhat.com>2014-08-13 10:21:35 -0400
committerJakub Hrozek <jhrozek@redhat.com>2014-08-19 15:54:55 +0200
commit86a2c33bdc84d486039279dd7bf4dbfcc41556c8 (patch)
treeeb38ee7914c00fd65fc61fbe95bed3d1dede4ff8
parentf7754c266d168c7e4ea09f39a968784370c81c71 (diff)
downloadsssd-86a2c33bdc84d486039279dd7bf4dbfcc41556c8.tar.gz
sssd-86a2c33bdc84d486039279dd7bf4dbfcc41556c8.tar.xz
sssd-86a2c33bdc84d486039279dd7bf4dbfcc41556c8.zip
MAN: How much time sssd spends offline
Added note to man page about how the time SSSD spends offline is calculated. Reviewed-by: Dan Lavu <side_control@runlevelone.net>
-rw-r--r--src/man/sssd.8.xml45
1 files changed, 41 insertions, 4 deletions
diff --git a/src/man/sssd.8.xml b/src/man/sssd.8.xml
index 0e584cd26..bdf83f189 100644
--- a/src/man/sssd.8.xml
+++ b/src/man/sssd.8.xml
@@ -189,10 +189,47 @@
<refsect1 id='notes'>
<title>NOTES</title>
- <para>
- If the environment variable SSS_NSS_USE_MEMCACHE is set to "NO",
- client applications will not use the fast in memory cache.
- </para>
+ <variablelist remap='IP'>
+ <varlistentry>
+ <term>Environment variable SSS_NSS_USE_MEMCACHE</term>
+ <listitem>
+ <para>
+ If the environment variable SSS_NSS_USE_MEMCACHE is set to "NO",
+ client applications will not use the fast in-memory cache.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Amount of time SSSD spends in offline mode</term>
+ <listitem>
+ <para>
+ When SSSD switches to offline mode, the amount of
+ time before it tries to go back online will
+ increase based upon the time spent disconnected.
+ This value is in seconds and calculated by the
+ following:
+ </para>
+ <para>
+ 60 + random_offset
+ </para>
+ <para>
+ The random offset can increment up to 30 seconds.
+ After each unsuccessful attempt to go online,
+ the new interval is recalculated by the following:
+ </para>
+ <para>
+ new_interval = old_interval*2 + random_offset
+ </para>
+ <para>
+ Note that the maximum length of each interval
+ is currently limited to one hour. If the
+ calculated length of new_interval is greater
+ than an hour, it will be forced to one hour.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
</refsect1>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="include/seealso.xml" />