1
0
mirror of https://github.com/samba-team/samba.git synced 2025-12-02 00:23:50 +03:00

idmap_tdb2.8: Remove part about alloc backend

Signed-off-by: Luk Claes <luk@debian.org>
Signed-off-by: Michael Adam <obnox@samba.org>
This commit is contained in:
Luk Claes
2011-05-31 00:26:29 +02:00
committed by Michael Adam
parent 09b2dd93df
commit a8d0d832e9

View File

@@ -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>