s3:docs: clarify explanation of the allocator in the idmap_ldap manpage

[ira/wip.git] / docs-xml / manpages-3 / idmap_ldap.8.xml

diff --git a/docs-xml/manpages-3/idmap_ldap.8.xml b/docs-xml/manpages-3/idmap_ldap.8.xml
index ea9e5bf07ea69229972af34398dbc6ea99dba9fe..0c8fa3c3ebc0828471438a11c7dfcbeb282b972d 100644 (file)
--- a/docs-xml/manpages-3/idmap_ldap.8.xml
+++ b/docs-xml/manpages-3/idmap_ldap.8.xml
@@ -22,9 +22,15 @@
        <para>The idmap_ldap plugin provides a means for Winbind to
        store and retrieve SID/uid/gid mapping tables in an LDAP directory
        service.
+       </para>
+
+       <para>
        In contrast to read only backends like idmap_rid, it is an allocating
-       backend: This means that it needs to allocate new user and group IDs to
-       create new mappings as requests to yet unmapped users are answered.
+       backend: This means that it needs to allocate new user and group IDs in
+       order to create new mappings. The allocator can be provided by the
+       idmap_ldap backend itself or by any other allocating backend like
+       idmap_tdb or idmap_tdb2. This is configured with the
+       parameter <parameter>idmap alloc backend</parameter>.
        </para>
 
        <para>