summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJakub Hrozek <jhrozek@redhat.com>2013-07-12 16:55:47 +0200
committerJakub Hrozek <jhrozek@redhat.com>2013-07-17 15:06:30 +0200
commitd1ccb40d426d7c67dfa0c86cdabbb3ed9a7585eb (patch)
tree6442097fa9e4807958176fc2785d4c2b57cebd66
parent02ec52b73c1714b877b0b7bc43fbc8d36ad8ca40 (diff)
downloadsssd-d1ccb40d426d7c67dfa0c86cdabbb3ed9a7585eb.tar.gz
sssd-d1ccb40d426d7c67dfa0c86cdabbb3ed9a7585eb.tar.bz2
sssd-d1ccb40d426d7c67dfa0c86cdabbb3ed9a7585eb.zip
MAN: Clarify the min_id/max_id limits further
https://fedorahosted.org/sssd/ticket/2005 Some users were confused by our description of min_id/max_id and thought the limits only applied to returning entries from the NSS responder. However, the limits are actually enforced on the back end side, so the entries are not even saved to cache.
-rw-r--r--src/man/sssd.conf.5.xml4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml
index 8df2bd97..a0321df8 100644
--- a/src/man/sssd.conf.5.xml
+++ b/src/man/sssd.conf.5.xml
@@ -914,6 +914,10 @@ override_homedir = /home/%u
range will be reported as expected.
</para>
<para>
+ These ID limits affect even saving entries to
+ cache, not only returning them by name or ID.
+ </para>
+ <para>
Default: 1 for min_id, 0 (no limit) for max_id
</para>
</listitem>