[SSSD] [PATCH] MAN: Document that sss_cache should be run after changing the cache timeout
Jakub Hrozek
jhrozek at redhat.com
Wed Sep 4 15:33:38 UTC 2013
Several users already stumbled upon the fact that the cache timeouts are
stored in the cache and one needs to run sss_cache after lowering the
timeout to reset the dataExpireTimestamp.
-------------- next part --------------
>From 2b7368a7a922cd32dd508809f5334df4c6fbc82a Mon Sep 17 00:00:00 2001
From: Jakub Hrozek <jhrozek at redhat.com>
Date: Wed, 4 Sep 2013 17:25:15 +0200
Subject: [PATCH] MAN: Document that sss_cache should be run after changing the
cache timeout
---
src/man/sssd.conf.5.xml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml
index a15f7288cc147b3f2944bb91cb861705279a3a37..43c06955d0182afe5a3c7d703f7c08b7cd09f503 100644
--- a/src/man/sssd.conf.5.xml
+++ b/src/man/sssd.conf.5.xml
@@ -1024,6 +1024,19 @@ override_homedir = /home/%u
entries valid before asking the backend again
</para>
<para>
+ The cache expiration timestamps are stored
+ as attributes of individual objects in the
+ cache. Therefore, changing the cache timeout only
+ has effect for newly added or expired entries.
+ You should run the
+ <citerefentry>
+ <refentrytitle>sss_cache</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>
+ tool in order to force refresh of entries that
+ have already been cached.
+ </para>
+ <para>
Default: 5400
</para>
</listitem>
--
1.8.3.1
More information about the sssd-devel
mailing list