summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuk Claes <luk@debian.org>2011-05-31 00:26:37 +0200
committerKarolin Seeger <kseeger@samba.org>2011-06-07 20:03:35 +0200
commitafee1312d65bd4ba26199308b399822e4dcc1124 (patch)
tree8285bae24a68da6f82e59944d626a927d0cbff78
parent2f5ec203fd3a7ffd49950009cfaea427ce564dfa (diff)
downloadsamba-afee1312d65bd4ba26199308b399822e4dcc1124.tar.gz
idmap_tdb.8: Remove references to alloc backend
Signed-off-by: Luk Claes <luk@debian.org> Signed-off-by: Michael Adam <obnox@samba.org> (cherry picked from commit 1ec7b0df60769b39ed0fd4be558abbb679dfe504)
-rw-r--r--docs-xml/manpages-3/idmap_tdb.8.xml20
1 files changed, 1 insertions, 19 deletions
diff --git a/docs-xml/manpages-3/idmap_tdb.8.xml b/docs-xml/manpages-3/idmap_tdb.8.xml
index 90d797f7f17..b58bdf56f6e 100644
--- a/docs-xml/manpages-3/idmap_tdb.8.xml
+++ b/docs-xml/manpages-3/idmap_tdb.8.xml
@@ -27,25 +27,7 @@
<para>
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 <parameter>idmap alloc backend</parameter>.
- </para>
-
- <para>
- 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 &quot;idmap uid&quot; and &quot;idmap gid&quot;.
- </para>
-
- <para>
- Furthermore, since there is only one global allocating backend
- responsible for all domains using writeable idmap backends,
- any explicitly configured domain with idmap backend tdb
- 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.
</para>
</refsynopsisdiv>