From 9c72dd78f25be4a7ffa5af5a242670ec76930d6f Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij <jelmer@samba.org>
Date: Sat, 12 Mar 2005 22:34:38 +0000
Subject: Use new definition of <smbconfoption>, fixes a bunch of validity
 errors. (This used to be commit 3eb5c35e47951f320f7c2f4cd478a95f6d48236e)

---
 docs/Samba-HOWTO-Collection/Bugs.xml | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

(limited to 'docs/Samba-HOWTO-Collection/Bugs.xml')

diff --git a/docs/Samba-HOWTO-Collection/Bugs.xml b/docs/Samba-HOWTO-Collection/Bugs.xml
index 0f8378993f..2fd313c257 100644
--- a/docs/Samba-HOWTO-Collection/Bugs.xml
+++ b/docs/Samba-HOWTO-Collection/Bugs.xml
@@ -80,36 +80,36 @@ detail, but may use too much disk space.
 </para>
 
 <para>
-To set the debug level, use the <smbconfoption><name>log level</name></smbconfoption> in your 
+To set the debug level, use the <smbconfoption name="log level"/> in your 
 &smb.conf;. You may also find it useful to set the log 
 level higher for just one machine and keep separate logs for each machine. 
 To do this, add the following lines to your main &smb.conf; file:
 </para>
 
 <para><smbconfblock>
-<smbconfoption><name>log level</name><value>10</value></smbconfoption>
-<smbconfoption><name>log file</name><value>/usr/local/samba/lib/log.%m</value></smbconfoption>
-<smbconfoption><name>include</name><value>/usr/local/samba/lib/smb.conf.%m</value></smbconfoption>
+<smbconfoption name="log level">10</smbconfoption>
+<smbconfoption name="log file">/usr/local/samba/lib/log.%m</smbconfoption>
+<smbconfoption name="include">/usr/local/samba/lib/smb.conf.%m</smbconfoption>
 </smbconfblock></para>
 
 <para>
 and create a file <filename>/usr/local/samba/lib/smb.conf.<replaceable>machine</replaceable></filename> where
 <replaceable>machine</replaceable> is the name of the client you wish to debug. In that file
 put any &smb.conf; commands you want, for example 
-<smbconfoption><name>log level</name></smbconfoption> may be useful. This also allows you to 
+<smbconfoption name="log level"/> may be useful. This also allows you to 
 experiment with different security systems, protocol levels and so on, on just 
 one machine.
 </para>
 
 <para>
-The &smb.conf; entry <smbconfoption><name>log level</name></smbconfoption> 
-is synonymous with the parameter <smbconfoption><name>debuglevel</name></smbconfoption> that has
+The &smb.conf; entry <smbconfoption name="log level"/> 
+is synonymous with the parameter <smbconfoption name="debuglevel"/> that has
 been used in older versions of Samba and is being retained for backward 
 compatibility of &smb.conf; files.
 </para>
 
 <para>
-As the <smbconfoption><name>log level</name></smbconfoption> value is increased, you will record 
+As the <smbconfoption name="log level"/> value is increased, you will record 
 a significantly greater level of debugging information. For most 
 debugging operations, you may not need a setting higher than 
 <constant>3</constant>. Nearly 
@@ -128,9 +128,9 @@ prepared for a large volume of log data.
 
 <para>
 <smbconfblock>
-<smbconfoption><name>log level</name><value>0 tdb:3 passdb:5 auth:4 vfs:2</value></smbconfoption>
-<smbconfoption><name>max log size</name><value>0</value></smbconfoption>
-<smbconfoption><name>log file</name><value>/var/log/samba/%U.%m.log</value></smbconfoption>
+<smbconfoption name="log level">0 tdb:3 passdb:5 auth:4 vfs:2</smbconfoption>
+<smbconfoption name="max log size">0</smbconfoption>
+<smbconfoption name="log file">/var/log/samba/%U.%m.log</smbconfoption>
 </smbconfblock>
 </para>
 
-- 
cgit