From b0eafa6e39384c4bf6bef7831351d684b1b63268 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 27 Jan 2005 20:19:12 +0000 Subject: Fix typo. (This used to be commit de095db88bdb3c097f32126f69b87422d48a854e) --- docs/Samba-Guide/Chap05-500UserNetwork.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/Samba-Guide/Chap05-500UserNetwork.xml b/docs/Samba-Guide/Chap05-500UserNetwork.xml index d03a2564a0..6ca3d72bb8 100644 --- a/docs/Samba-Guide/Chap05-500UserNetwork.xml +++ b/docs/Samba-Guide/Chap05-500UserNetwork.xml @@ -194,7 +194,7 @@ network load factors 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 -- cgit