s3:docs:idmap_tdb2: update the documentation of idmap script

to reflect the new variant "idmap config * : script" of configuring the idmap script
(cherry picked from commit 2aa19b4aeb9de43a0e2b94ad1202f2068b29c710)

diff --git a/docs-xml/manpages-3/idmap_tdb2.8.xml b/docs-xml/manpages-3/idmap_tdb2.8.xml
index 980ffe6eff8062c3ca2b375043118705378b2e70..18cfe0db725cedf776063a95dc3a47eb98773a4c 100644 (file)
--- a/docs-xml/manpages-3/idmap_tdb2.8.xml
+++ b/docs-xml/manpages-3/idmap_tdb2.8.xml
@@ -43,6 +43,16 @@
                        backend is authoritative.
                </para></listitem>
                </varlistentry>
+
+               <varlistentry>
+               <term>script</term>
+               <listitem><para>
+                       This option can be used to configure an external program
+                       for performing id mappings instead of using the tdb
+                       counter. The mappings are then stored int tdb2 idmap
+                       database. For details see the section on IDMAP SCRIPT below.
+               </para></listitem>
+               </varlistentry>
        </variablelist>
 </refsect1>
 
@@ -50,8 +60,12 @@
        <title>IDMAP SCRIPT</title>
 
        <para>
-       The tdb2 idmap backend supports a script for performing id mappings
-       through the smb.conf option <parameter>idmap : script</parameter>.
+       The tdb2 idmap backend supports an external program for performing id mappings
+       through the smb.conf option <parameter>idmap config * : script</parameter> or
+       its deprecated legacy form <parameter>idmap : script</parameter>.
+       </para>
+
+       <para>
        The script should accept the following command line options.
        </para>