Fix escaped backslashes (bug #5194). Thanks to the Debian Samba package maintainers...

Karolin
(This used to be commit e55ce8eda2406d1f9d2da08aae01b4026aa38262)

diff --git a/docs/smbdotconf/security/usernamemap.xml b/docs/smbdotconf/security/usernamemap.xml
index 59c0cdde7c5133b9da3ce5a348dd3dc24c87cc8c..54179690be569688c0d362e110c547e5911ce4d1 100644 (file)
--- a/docs/smbdotconf/security/usernamemap.xml
+++ b/docs/smbdotconf/security/usernamemap.xml
@@ -15,7 +15,7 @@
        Please note that for user or share mode security, the username map is applied prior to validating the user
        credentials.  Domain member servers (domain or ads) apply the username map after the user has been
        successfully authenticated by the domain controller and require fully qualified enties in the map table (e.g.
-       biddle = DOMAIN\foo).
+       biddle = <literal>DOMAIN\foo</literal>).
        </para>
     
     <para>
@@ -96,7 +96,8 @@ guest = *
        </para>
 
    <para>
-       Samba versions prior to 3.0.8 would only support reading the fully qualified username (e.g.: DOMAIN\user) from
+       Samba versions prior to 3.0.8 would only support reading the fully qualified username 
+       (e.g.: <literal>DOMAIN\user</literal>) from
        the username map when performing a kerberos login from a client.  However, when looking up a map entry for a
        user authenticated by NTLM[SSP], only the login name would be used for matches.  This resulted in inconsistent
        behavior sometimes even on the same server.
@@ -113,7 +114,7 @@ guest = *
 
     <para>
     When relying upon a external domain controller for validating authentication requests, smbd will apply the username map
-    to the fully qualified username (i.e. DOMAIN\user) only after the user has been successfully authenticated.
+    to the fully qualified username (i.e. <literal>DOMAIN\user</literal>) only after the user has been successfully authenticated.
     </para>
 
     <para>