From a52a587783e058f75815fa8add1f46b1c1d6f2d3 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Tue, 7 Dec 2010 17:30:27 +0100 Subject: [PATCH] docs: clarify the idmap_rid manpage (bug #7788) The idmap_rid module should not be used as a default backend. Also mention that the old snytax "idmap backend = rid:domain=range ..." is not supported any more. Autobuild-User: Michael Adam Autobuild-Date: Tue Dec 7 19:07:57 CET 2010 on sn-devel-104 --- docs-xml/manpages-3/idmap_rid.8.xml | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/docs-xml/manpages-3/idmap_rid.8.xml b/docs-xml/manpages-3/idmap_rid.8.xml index 33200b8..a2a1c58 100644 --- a/docs-xml/manpages-3/idmap_rid.8.xml +++ b/docs-xml/manpages-3/idmap_rid.8.xml @@ -21,6 +21,24 @@ The idmap_rid backend provides a way to use an algorithmic mapping scheme to map UIDs/GIDs and SIDs. No database is required in this case as the mapping is deterministic. + + + Note that the idmap_rid module has changed considerably since Samba + versions 3.0. and 3.2. + Currently, there should to be an explicit idmap configuration for each + domain that should use the idmap_rid backend, using disjoint ranges. + One usually needs to define a writeable default idmap range, using + a backent like tdb or ldap + that can create unix ids, in order to be able to map the BUILTIN sids + and other domains, and also in order to be able to create group mappings. + See the example below. + + + + Note that the old syntax + idmap backend = rid:"DOM1=range DOM2=range2 ..." + is not supported any more since Samba version 3.0.25. + -- 1.6.3.3