ChangeLogTag: Wed Jun 30 10:18:12 UTC 2004 Johnny Willemsen <jwillemsen@remedy.nl>

1 files changed, 11 insertions, 11 deletions

diff --git a/TAO/orbsvcs/tests/Redundant_Naming/README b/TAO/orbsvcs/tests/Redundant_Naming/README
index ce0c91729b5..85ad95373a1 100644
--- a/TAO/orbsvcs/tests/Redundant_Naming/README
+++ b/TAO/orbsvcs/tests/Redundant_Naming/README
@@ -10,8 +10,8 @@ To run tests manually -
 	TAO/orbsvcs/Naming_Service/README for valid options),
 	then run ./client the optional options are shown below.
 
-NOTE: if running tests manually, the NameService directory must exist 
-before starting the Naming Service and this directory must be cleaned out 
+NOTE: if running tests manually, the NameService directory must exist
+before starting the Naming Service and this directory must be cleaned out
 manually after stopping the Naming Service.
 
 The following options exist:
@@ -26,17 +26,17 @@ The following options exist:
 
 -q      ior for Naming Server 2
 
-The client creates two context trees, one of breath b and one of depth d, 
-and another node with o objects.  It then removes the contexts b-1, d and 
-the object o-1.  All these are done using the first name server.  The 
-client then accesses contexts b, b-1, d, d-1, and objects o, o-1 looking 
+The client creates two context trees, one of breath b and one of depth d,
+and another node with o objects.  It then removes the contexts b-1, d and
+the object o-1.  All these are done using the first name server.  The
+client then accesses contexts b, b-1, d, d-1, and objects o, o-1 looking
 for the appropriate found/not-found returns using the second name server.
 
         Example (on a Unix system):
         $ $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service -o nsior1\
-          -R NameService -ORBEndPoint iiop://localhost:10001 &
+          -r NameService -ORBEndPoint iiop://localhost:10001 &
         $ $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service -o nsior2\
-          -R NameService -ORBEndPoint iiop://localhost:10002 &
+          -r NameService -ORBEndPoint iiop://localhost:10002 &
         $ ./client -p file://nsior1 -q file://nsior2
 
         where the steps correspond to 1&2)starting the Naming Service
@@ -56,17 +56,17 @@ The default test runs in a few seconds.  (4 on my 500MHz Linux)
 *****************************
 Restrictions, performance notes, and future
 
-While the redundant naming service is only fully function on Tru64 
+While the redundant naming service is only fully function on Tru64
 clusters, it can be used on any two systems that share a file system
 with locking.  However, this test puts the two naming servers on the
-local system doesn't test the locking (probablistic to do, at best) 
+local system doesn't test the locking (probablistic to do, at best)
 and runs the client on the same system.  This will specifically test
 only the functionality of the redundancy.  The extra parameters can
 be used manually to probe performance, as illustrated below.
 
 Using the b,d, and o options, I determined:
 
-As the number of objects in a single context increases, performance 
+As the number of objects in a single context increases, performance
 decreases.  This is because of I/O limits, each addition of a new
 object reference adds about 1/2 KB and rewrites the whole file.  I
 observed 9746 objects added to a single context in 100 minutes and