diff options
author | Jakub Hrozek <jhrozek@redhat.com> | 2013-09-04 17:25:15 +0200 |
---|---|---|
committer | Jakub Hrozek <jhrozek@redhat.com> | 2013-09-05 11:11:40 +0200 |
commit | 21e9b2c71dfabd3e6b39f6e2911edbb28f3439d3 (patch) | |
tree | 31739f64b7ebf996275df0052a97d60dbe6889e4 | |
parent | bb421d65102218cc50ed4a7840090a6cdb6a04c4 (diff) | |
download | sssd-21e9b2c71dfabd3e6b39f6e2911edbb28f3439d3.tar.gz sssd-21e9b2c71dfabd3e6b39f6e2911edbb28f3439d3.tar.bz2 sssd-21e9b2c71dfabd3e6b39f6e2911edbb28f3439d3.zip |
MAN: Document that sss_cache should be run after changing the cache timeout
-rw-r--r-- | src/man/sssd.conf.5.xml | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml index a15f7288..43c06955 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> |