From 340931bd335e9906cc72e7d4f7f1ae15d2906dcd Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Wed, 21 Jan 2009 10:49:48 +0100 Subject: s3:docs: clarify explanation of allocator in the idmap_tdb2 manpage Michael (cherry picked from commit 65b79200e46751278c125ad260d899d10d6466a2) Signed-off-by: Michael Adam (cherry picked from commit 73a835335e329f0aaa0b72ebfd538b8c2b813812) --- docs-xml/manpages-3/idmap_tdb2.8.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs-xml/manpages-3/idmap_tdb2.8.xml b/docs-xml/manpages-3/idmap_tdb2.8.xml index 3e61f7f527a..4f19ba103ab 100644 --- a/docs-xml/manpages-3/idmap_tdb2.8.xml +++ b/docs-xml/manpages-3/idmap_tdb2.8.xml @@ -26,10 +26,12 @@ - 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. + 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 in + order to create new mappings. The allocator can be provided by the + idmap_tdb2 backend itself or by any other allocating backend like + idmap_tdb or idmap_ldap. This is configured with the + parameter idmap alloc backend. -- cgit