From 55d8ee039a920508fb51bcc85397e26acc365f60 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij <jelmer@samba.org>
Date: Mon, 4 Jul 2005 21:36:46 +0000
Subject: Some random updates. (This used to be commit
 57d0cc9fcdc1c790a601f6dcf7071188448a5f58)

---
 docs/smbdotconf/browse/domainmaster.xml | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

(limited to 'docs/smbdotconf/browse/domainmaster.xml')

diff --git a/docs/smbdotconf/browse/domainmaster.xml b/docs/smbdotconf/browse/domainmaster.xml
index 54f97caf37..d946ced7e6 100644
--- a/docs/smbdotconf/browse/domainmaster.xml
+++ b/docs/smbdotconf/browse/domainmaster.xml
@@ -8,9 +8,9 @@
 	<manvolnum>8</manvolnum></citerefentry> to enable WAN-wide browse list
 	collation. Setting this option causes <command moreinfo="none">nmbd</command> to
 	claim a special domain specific NetBIOS name that identifies 
-	it as a domain master browser for its given <link linkend="WORKGROUP">
-	<parameter moreinfo="none">workgroup</parameter></link>. Local master browsers 
-	in the same <parameter moreinfo="none">workgroup</parameter> on broadcast-isolated 
+	it as a domain master browser for its given 
+		<smbconfoption name="workgroup"/>. Local master browsers 
+		in the same <smbconfoption name="workgroup"/> on broadcast-isolated 
 	subnets will give this <command moreinfo="none">nmbd</command> their local browse lists, 
 	and then ask <citerefentry><refentrytitle>smbd</refentrytitle>
 	<manvolnum>8</manvolnum></citerefentry> for a complete copy of the browse 
@@ -19,20 +19,19 @@
 	instead of just the list for their broadcast-isolated subnet.</para>
 
 	<para>Note that Windows NT Primary Domain Controllers expect to be 
-	able to claim this <parameter moreinfo="none">workgroup</parameter> specific special 
+		able to claim this <smbconfoption name="workgroup"/> specific special 
 	NetBIOS name that identifies them as domain master browsers for 
-	that <parameter moreinfo="none">workgroup</parameter> by default (i.e. there is no 
+	that <smbconfoption name="workgroup"/> by default (i.e. there is no 
 	way to prevent a Windows NT PDC from attempting to do this). This 
 	means that if this parameter is set and <command moreinfo="none">nmbd</command> claims 
-	the special name for a <parameter moreinfo="none">workgroup</parameter> before a Windows 
+	the special name for a <smbconfoption name="workgroup"/> before a Windows 
 	NT PDC is able to do so then cross subnet browsing will behave 
 	strangely and may fail.</para>
 		
-	<para>If <link linkend="DOMAINLOGONS"><command moreinfo="none">domain logons = yes</command>
-	</link>, then the default behavior is to enable the <parameter moreinfo="none">domain 
-	master</parameter> parameter.  If <parameter moreinfo="none">domain logons</parameter> is 
-	not enabled (the default setting), then neither will <parameter moreinfo="none">domain 
-	master</parameter> be enabled by default.</para>
+<para>If <smbconfoption name="domain logons">yes</smbconfoption>
+	, then the default behavior is to enable the <smbconfoption name="domain 
+		master"/> parameter.  If <smbconfoption name="domain logons"/> is 
+	not enabled (the default setting), then neither will <smbconfoption name="domain master"/> be enabled by default.</para>
 
 </description>
 <value type="default">auto</value>
-- 
cgit