From 816934faa8bbe53dd299bc5e39f471eafdddefa8 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Wed, 21 Jan 2009 10:56:34 +0100 Subject: [PATCH] s3:docs: clarify explanation of the allocator in the idmap_ldap manpage Michael --- docs-xml/manpages-3/idmap_ldap.8.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs-xml/manpages-3/idmap_ldap.8.xml b/docs-xml/manpages-3/idmap_ldap.8.xml index ea9e5bf07ea..0c8fa3c3ebc 100644 --- a/docs-xml/manpages-3/idmap_ldap.8.xml +++ b/docs-xml/manpages-3/idmap_ldap.8.xml @@ -22,9 +22,15 @@ The idmap_ldap plugin provides a means for Winbind to store and retrieve SID/uid/gid mapping tables in an LDAP directory service. + + + 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 idmap alloc backend. -- 2.34.1