s3:doc: clarify the idmap script section in the idmap_tdb2 manpage

diff --git a/docs-xml/manpages-3/idmap_tdb2.8.xml b/docs-xml/manpages-3/idmap_tdb2.8.xml
index 18cfe0db725cedf776063a95dc3a47eb98773a4c..d979739b197faaf930bf76ce32d79f57ec918e8d 100644 (file)
--- a/docs-xml/manpages-3/idmap_tdb2.8.xml
+++ b/docs-xml/manpages-3/idmap_tdb2.8.xml
@@ -65,6 +65,15 @@
        its deprecated legacy form <parameter>idmap : script</parameter>.
        </para>
 
+       <para>
+       The mappings obtained by the script are then stored in the idmap tdb2
+       database instead of mappings created by the incrementing id counters.
+       It is therefore important that the script covers the complete range of
+       SIDs that can be passed in for SID to Unix ID mapping, since otherwise
+       SIDs unmapped by the script might get mapped to IDs that had
+       previously been mapped by the script.
+       </para>
+
        <para>
        The script should accept the following command line options.
        </para>
@@ -86,13 +95,6 @@
        SID:yyyy
        ERR:yyyy
        </programlisting>
-
-       <para>
-       Note that the script should cover the complete range of SIDs
-       that can be passed in for SID to Unix ID mapping, since otherwise
-       SIDs unmapped by the script might get mapped to IDs that had
-       previously been mapped by the script.
-       </para>
 </refsect1>
 
 <refsect1>