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 <obnox@samba.org>
Autobuild-Date: Tue Dec  7 19:07:57 CET 2010 on sn-devel-104
(cherry picked from commit a4f48b3da0081845336c55ff230179caeab5195c)

diff --git a/docs-xml/manpages-3/idmap_rid.8.xml b/docs-xml/manpages-3/idmap_rid.8.xml
index 55aed62f85632fc9ce7e331e4629b4d565c94ef8..a453e914528594a54bc943a363b317a12566035c 100644 (file)
--- a/docs-xml/manpages-3/idmap_rid.8.xml
+++ b/docs-xml/manpages-3/idmap_rid.8.xml
@@ -21,6 +21,24 @@
        <para>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.</para>
+
+       <para>
+       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 <parameter>tdb</parameter> or <parameter>ldap</parameter>
+       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.
+       </para>
+
+       <para>
+       Note that the old syntax
+       <parameter>idmap backend = rid:"DOM1=range DOM2=range2 ..."</parameter>
+       is not supported any more since Samba version 3.0.25.
+       </para>
 </refsynopsisdiv>
 
 <refsect1>