On Mon, Jan 28, 2013 at 12:20:22PM +0100, Pavel Březina wrote: > On 01/25/2013 05:33 PM, Jakub Hrozek wrote: > >I think the other enumeration disadvantages are documented well enough > >in the manpage. I'm also thinking we might just say clear that in large > >environments, enumeration should be discouraged. Thoughts? > > +1 > > The patch itself looks good. But can you amend the commit message to > include link to the ticket please?
OK, new patch is attached.
>From 183172a1359d607a62bab2c6ce374d68d759b064 Mon Sep 17 00:00:00 2001 From: Jakub Hrozek <[email protected]> Date: Fri, 25 Jan 2013 17:31:38 +0100 Subject: [PATCH] MAN: Clarify that saving users after enumerating large domain might be CPU intensive https://fedorahosted.org/sssd/ticket/1732 --- src/man/sssd.conf.5.xml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml index 29563e56958aef288d7cad1f19c067c45efb5ca4..542edb8871e1bb3d8ee585fe0286eb2a7c4da333 100644 --- a/src/man/sssd.conf.5.xml +++ b/src/man/sssd.conf.5.xml @@ -958,7 +958,10 @@ override_homedir = /home/%u During this time, individual requests for information will go directly to LDAP, though it may be slow, due to the heavy enumeration - processing. + processing. Saving a large number of entries + to cache after the enumeration completes might + also be CPU intensive as the memberships have + to be recomputed. </para> <para> While the first enumeration is running, requests @@ -973,6 +976,11 @@ override_homedir = /home/%u For more information, refer to the man pages for the specific id_provider in use. </para> + <para> + For the reasons cited above, enabling enumeration + is not recommended, especially in large + environments. + </para> </listitem> </varlistentry> <varlistentry> -- 1.8.1
_______________________________________________ sssd-devel mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
