From a8d0d832e9dbb864b878da04c3e06a170fd66c66 Mon Sep 17 00:00:00 2001 From: Luk Claes Date: Tue, 31 May 2011 00:26:29 +0200 Subject: [PATCH] idmap_tdb2.8: Remove part about alloc backend Signed-off-by: Luk Claes Signed-off-by: Michael Adam --- docs-xml/manpages-3/idmap_tdb2.8.xml | 20 +------------------- 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/docs-xml/manpages-3/idmap_tdb2.8.xml b/docs-xml/manpages-3/idmap_tdb2.8.xml index 3be4f3013d0..b4a46f81aa9 100644 --- a/docs-xml/manpages-3/idmap_tdb2.8.xml +++ b/docs-xml/manpages-3/idmap_tdb2.8.xml @@ -28,25 +28,7 @@ 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. - - - - Note that in order for this (or any other allocating) backend to - function at all, the default backend needs to be writeable. - The ranges used for uid and gid allocation are the default ranges - configured by "idmap uid" and "idmap gid". - - - - Furthermore, since there is only one global allocating backend - responsible for all domains using writeable idmap backends, - any explicitly configured domain with idmap backend tdb2 - should have the same range as the default range, since it needs - to use the global uid / gid allocator. See the example below. + order to create new mappings. -- 2.34.1