summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuk Claes <luk@debian.org>2011-05-31 00:26:29 +0200
committerKarolin Seeger <kseeger@samba.org>2011-06-07 20:03:09 +0200
commit3392c25e2e8c356eefb240ef57cc3fd0a1704da8 (patch)
treecde1ad14e286a7280ff83bb7605e1432002625c3
parent90fc910779ff47b8c7a2ee9764ff537267846418 (diff)
downloadsamba-3392c25e2e8c356eefb240ef57cc3fd0a1704da8.tar.gz
idmap_tdb2.8: Remove part about alloc backend
Signed-off-by: Luk Claes <luk@debian.org> Signed-off-by: Michael Adam <obnox@samba.org> (cherry picked from commit 811a8c86cb16b9271bfe7441c8d53803b97fb5a3)
-rw-r--r--docs-xml/manpages-3/idmap_tdb2.8.xml20
1 files changed, 1 insertions, 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 @@
<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_tdb2 backend itself or by any other allocating backend like
- idmap_tdb or idmap_ldap. 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 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.
</para>
</refsynopsisdiv>