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

Michael
(cherry picked from commit 816934faa8bbe53dd299bc5e39f471eafdddefa8)

Signed-off-by: Michael Adam <obnox@samba.org>

diff --git a/docs-xml/manpages-3/idmap_ldap.8.xml b/docs-xml/manpages-3/idmap_ldap.8.xml
index 4d6167353c793318228e74c1867a1aba8e254b07..603f80023243c5b6f464208c018404c1e67b07e3 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>