svn commit: samba-docs r341 - in trunk/Samba-Guide: .

[jht at samba.org]

Author: jht
Date: 2005-01-27 20:19:12 +0000 (Thu, 27 Jan 2005)
New Revision: 341

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-docs&rev=341

Log:
Fix typo.
Modified:
   trunk/Samba-Guide/Chap05-500UserNetwork.xml


Changeset:
Modified: trunk/Samba-Guide/Chap05-500UserNetwork.xml
===================================================================
--- trunk/Samba-Guide/Chap05-500UserNetwork.xml	2005-01-27 16:03:15 UTC (rev 340)
+++ trunk/Samba-Guide/Chap05-500UserNetwork.xml	2005-01-27 20:19:12 UTC (rev 341)
@@ -194,7 +194,7 @@
 	<indexterm><primary>network load factors</primary></indexterm>
 	The example you are building in this chapter is an example of a network design that works,
 	but this does not make it a design that is recommended. As a general rule, there should
-	be at least one Backup Domain Controller per 50 Windows network clients. The principle behind
+	be at least one Backup Domain Controller per 150 Windows network clients. The principle behind
 	this recommendation is the fact that correct operation of MS Windows clients requires rapid
 	network response to all SMB/CIFS requests. The same rule says that if there are more than
 	50 clients per Domain Controller they are too busy to service requests. Let's put such