diff options
| author | Luk Claes <luk@debian.org> | 2011-05-31 00:26:37 +0200 |
|---|---|---|
| committer | Michael Adam <obnox@samba.org> | 2011-05-31 01:44:28 +0200 |
| commit | c42c8c957efb9a901d09ffdef9e566c71c7c8130 (patch) | |
| tree | 5339161eb4f0f7a4e7d9bb9243abe243a059e8fc | |
| parent | d73a891e38048702b03a7cd0d99f121ec2bf782c (diff) | |
| download | samba-c42c8c957efb9a901d09ffdef9e566c71c7c8130.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>
| -rw-r--r-- | docs-xml/manpages-3/idmap_tdb.8.xml | 20 |
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 "idmap uid" and "idmap gid". - </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> |