From 665b5dc70333ca36129a6fe06645bd9faa4f2350 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Wed, 21 Jan 2009 10:55:19 +0100 Subject: s3:docs: clarify explanation of the allocator in the idmap_tdb manpage Michael --- docs-xml/manpages-3/idmap_tdb.8.xml | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'docs-xml/manpages-3/idmap_tdb.8.xml') diff --git a/docs-xml/manpages-3/idmap_tdb.8.xml b/docs-xml/manpages-3/idmap_tdb.8.xml index fb23076d08..2b4c050966 100644 --- a/docs-xml/manpages-3/idmap_tdb.8.xml +++ b/docs-xml/manpages-3/idmap_tdb.8.xml @@ -21,10 +21,16 @@ The idmap_tdb plugin is the default backend used by winbindd - for storing SID/uid/gid mapping tables. 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. + for storing SID/uid/gid mapping tables. + + + + 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_tdb backend itself or by any other allocating backend like + idmap_ldap or idmap_tdb2. This is configured with the + parameter idmap alloc backend. -- cgit