From cfef10a0a2a16221eac27b6b7d3b3d7d952a418e Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Tue, 31 May 2011 18:09:14 +0200 Subject: s3:doc: clean up the example section of the idmap_tdb manpage Autobuild-User: Michael Adam Autobuild-Date: Tue May 31 19:47:45 CEST 2011 on sn-devel-104 --- docs-xml/manpages-3/idmap_tdb.8.xml | 23 +---------------------- 1 file changed, 1 insertion(+), 22 deletions(-) (limited to 'docs-xml') diff --git a/docs-xml/manpages-3/idmap_tdb.8.xml b/docs-xml/manpages-3/idmap_tdb.8.xml index cd024e8b3b..c67d6cb9bc 100644 --- a/docs-xml/manpages-3/idmap_tdb.8.xml +++ b/docs-xml/manpages-3/idmap_tdb.8.xml @@ -50,8 +50,7 @@ This example shows how tdb is used as a the default idmap backend. - It configures the idmap range through the global options for all - domains encountered. This same range is used for uid/gid allocation. + This configured range is used for uid and gid allocation. @@ -60,26 +59,6 @@ idmap config * : backend = tdb idmap config * : range = 1000000-2000000 - - - This (rather theoretical) example shows how tdb can be used as the - allocating backend while ldap is the default backend used to store - the mappings. - It adds an explicit configuration for some domain DOM1, that - uses the tdb idmap backend. Note that the same range as the - default uid/gid range is used, since the allocator has to serve - both the default backend and the explicitly configured domain DOM1. - - - - [global] - idmap config * : backend = ldap - idmap config * : range = 1000000-2000000 - # use a different uid/gid allocator: - - idmap config DOM1 : backend = tdb - idmap config DOM1 : range = 1000000-2000000 - -- cgit