Fixed fuzz

10 files changed, 65 insertions, 63 deletions

diff --git a/TAO/orbsvcs/IFR_Service/README b/TAO/orbsvcs/IFR_Service/README
index c846bdde6f1..98d84c6f321 100644
--- a/TAO/orbsvcs/IFR_Service/README
+++ b/TAO/orbsvcs/IFR_Service/README
@@ -1,14 +1,13 @@
 $Id$
 
-
 Interface Repository -------
 
 Required libraries (in addition to ACE and TAO):
-        ACE_ROOT/TAO/tao/IFR_CLient/TAO_IFR_CLient.(lib-ext)     
-        ACE_ROOT/TAO/tao/TypeCodeFactory/TAO_TypeCodeFactory.(lib-ext)       
-        ACE_ROOT/TAO/tao/PortableServer/TAO_PortableServer.(lib-ext)    
-        ACE_ROOT/TAO/tao/IORTable/TAO_IORTable.(lib-ext)    
-        ACE_ROOT/TAO/orbsvcs/orbsvcs/TAO_Svc_Utils.(lib-ext)    
+        ACE_ROOT/TAO/tao/IFR_CLient/TAO_IFR_CLient.(lib-ext)
+        ACE_ROOT/TAO/tao/TypeCodeFactory/TAO_TypeCodeFactory.(lib-ext)
+        ACE_ROOT/TAO/tao/PortableServer/TAO_PortableServer.(lib-ext)
+        ACE_ROOT/TAO/tao/IORTable/TAO_IORTable.(lib-ext)
+        ACE_ROOT/TAO/orbsvcs/orbsvcs/TAO_Svc_Utils.(lib-ext)
 
 Executable name is IFR_Service.
 
@@ -16,7 +15,7 @@ Command line options are:
 
  -p		Makes the Interface Repository persistent.
 
- -b <filename>	Overrides the default filename used for 
+ -b <filename>	Overrides the default filename used for
 		persistent storage. The default filename
 		is "ifr_default_backing_store".
 
@@ -34,8 +33,8 @@ Command line options are:
 		If the platform is not win32, an error
 		message is output.
 
- -o <filename>	Overrides the default filename used for 
-		outputting the Interface Repository IOR. 
+ -o <filename>	Overrides the default filename used for
+		outputting the Interface Repository IOR.
 		The default filename is "if_repo.ior".
 
 Test code for the Interface Repository can be found in
@@ -54,12 +53,12 @@ the IFR service, plus the IFR_Service executable itself.
 Test code for tao_ifr can be found in
 ACE_ROOT/TAO/orbsvcs/tests/InterfaceRepo/Application_Test.
 
-tao_ifr can also handle the -ORBxxx parameters. The one most 
-frequently used would probably be 
+tao_ifr can also handle the -ORBxxx parameters. The one most
+frequently used would probably be
 
 '-ORBInitRef InterfaceRepository=file://<filename>'
 
-which will enable the IFR service to be resolved by getting 
+which will enable the IFR service to be resolved by getting
 its IOR from <filename>. By default, the IFR service stores
 its IOR in the file 'if_repo.ior', but that can be modified
 by starting the IFR service using the -o option (see above).
@@ -70,10 +69,10 @@ tao_ifr can process multiple IDL files in one execution. As
 long as the filenames come after any -ORB options that may
 be present, they may come mixed in any order with the other
 command line options. The tao_ifr command line parser will
-treat any option (or option pair) that doesn't begin with 
+treat any option (or option pair) that doesn't begin with
 '-' as a filename.
 
-More information about the Interface Repository and tao_ifr can 
+More information about the Interface Repository and tao_ifr can
 be found in ACE_ROOT/TAO/docs/releasenotes/index.html.
 
 
diff --git a/TAO/orbsvcs/examples/CosEC/TypedSimple/README b/TAO/orbsvcs/examples/CosEC/TypedSimple/README
index d722b0a9e0c..99d74a87b64 100644
--- a/TAO/orbsvcs/examples/CosEC/TypedSimple/README
+++ b/TAO/orbsvcs/examples/CosEC/TypedSimple/README
@@ -1,7 +1,7 @@
-# $Id$
+$Id$
 
-	This directory contains an example for a COS Event Service, 
-using a typed channel. 
+	This directory contains an example for a COS Event Service,
+using a typed channel.
 It contains two executables; a consumer and a supplier.
 
 	To test it use :
@@ -9,7 +9,7 @@ It contains two executables; a consumer and a supplier.
 # rm Country.ifr
 # IFR_Service -p -b Country.ifr -ORBEndPoint iiop://localhost:12345
 # tao_ifr -ORBInitRef InterfaceRepository=corbaloc:iiop:localhost:12345/InterfaceRepository -I$TAO_ROOT/orbsvcs Country.idl
-# Naming_Service -ORBEndPoint iiop://localhost:8000 
+# Naming_Service -ORBEndPoint iiop://localhost:8000
 # CosEvent_Service -n CountryEventChannel -r -t -d -ORBInitRef InterfaceRepository=corbaloc:iiop:localhost:12345/InterfaceRepository -ORBInitRef NameService=corbaloc:iiop:localhost:8000/NameService
 # consumer -ORBInitRef NameService=corbaloc:iiop:localhost:8000/NameService
 # supplier -ORBInitRef NameService=corbaloc:iiop:localhost:8000/NameService
diff --git a/TAO/orbsvcs/examples/ImR/Advanced/README b/TAO/orbsvcs/examples/ImR/Advanced/README
index 08a1a004523..af0cb940210 100644
--- a/TAO/orbsvcs/examples/ImR/Advanced/README
+++ b/TAO/orbsvcs/examples/ImR/Advanced/README
@@ -1,3 +1,5 @@
+$Id$
+
 This example tests several uses of the Implementation Repository.
 
 How to Run
@@ -9,7 +11,7 @@ Driver files are stored in the drivers directory.
 Each file contains a set of parameters for each execution of the
 test.
 
-Each line item in the file has one of the follow forms. 
+Each line item in the file has one of the follow forms.
 Empty lines are ignored.
 
     # <Comment>
@@ -33,5 +35,5 @@ Empty lines are ignored.
 
 Execute the example script
 ----------------------------------------------------------------------
-The run_test.pl script reads the driver file and executes each line. 
+The run_test.pl script reads the driver file and executes each line.
 Simply execute run_test.pl to run all test in the drivers directory.
diff --git a/TAO/orbsvcs/examples/RtEC/MCast/README b/TAO/orbsvcs/examples/RtEC/MCast/README
index 55aad804e20..0c99de8bdca 100644
--- a/TAO/orbsvcs/examples/RtEC/MCast/README
+++ b/TAO/orbsvcs/examples/RtEC/MCast/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 	This directory contains a very simple example of a
 multicast-based federation of event services.
@@ -18,7 +18,7 @@ $ MCast
 	If you need to set the multicast group and port you can use
 the -m option:
 
-$ MCast -m 224.100.2.1:12345 
+$ MCast -m 224.100.2.1:12345
 
 	Run the test in multiple machines on the same network.  If
 there is only one process you should only receive 1000 events in the
diff --git a/TAO/orbsvcs/examples/Security/SecurityLevel1/README b/TAO/orbsvcs/examples/Security/SecurityLevel1/README
index a29c58d2ee7..5e3dcf1bebd 100644
--- a/TAO/orbsvcs/examples/Security/SecurityLevel1/README
+++ b/TAO/orbsvcs/examples/Security/SecurityLevel1/README
@@ -11,11 +11,11 @@ methods, it has to be authenticated first(I am not sure, as of now,
 the way for authenticating or the fact if this is really needed
 .. well for starters, I will leave authentication). Then based on the
 principals privilege attributes, the invocation will be
-successful or denied. 
+successful or denied.
 
 This test makes use of the Current::get_attributes to get the
 attributes of the prinicipal which are used to provide or deny
-access. 
+access.
 
 We will check the values for all the possible attribute types that a
 server could check in the remote case. And, as in the example, run
@@ -26,7 +26,7 @@ returning the correct credentials and not garbling or giving some
 random values.
 
 This will prove that
- 
+
 1. Authorization is working.
 2. All the attribute types which are supposed to work are working
    properly.
@@ -37,7 +37,7 @@ This will prove that
 
 	Since, the only thing that the SecurityLevel1 does is to get the
 credentials of the initiating principal, to test the implementation,
-in my view, 
+in my view,
 
 1. We need to see if the method is returning the correct credentials.
 2. If all the attribute types are working... ie.. show what are the
diff --git a/TAO/orbsvcs/examples/Security/Send_File/README b/TAO/orbsvcs/examples/Security/Send_File/README
index c02ca187f21..41ebd561bc8 100644
--- a/TAO/orbsvcs/examples/Security/Send_File/README
+++ b/TAO/orbsvcs/examples/Security/Send_File/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Description:
 
@@ -58,7 +58,7 @@ $ client -k file://test.ior < certificate.pem
 
 ======= Testing failed authentications:
 
-	To test failed server authentications we simply run the client 
+	To test failed server authentications we simply run the client
 and server as indicated below, but we enter invalid pass phrases in
 the client and/or server.
 
diff --git a/TAO/orbsvcs/tests/Bug_2925_Regression/README b/TAO/orbsvcs/tests/Bug_2925_Regression/README
index dae972d52fe..57bb002b2c4 100644
--- a/TAO/orbsvcs/tests/Bug_2925_Regression/README
+++ b/TAO/orbsvcs/tests/Bug_2925_Regression/README
@@ -11,9 +11,9 @@ _Expected successful result_:
 
 D:\devel\DOCGroup\check\tao_ipv6\TAO\orbsvcs\tests\Bug_2925_Regression>run_test.pl
 Activated as <IOR:00000000000000010000000000000001000000030000004c000102000000000f3233302e3235352e3235352e333300001ce20000000000010000002700000024000100000000000d63646d776674646f6d61696e0033302e000000000000000100000000>
-00<<; 00>>; 01<<; 01>>; 02<<; 02>>; 03<<; 03>>; 04<<; 04>>; 05<<; 05>>; 06<<; 06>>; 07<<; 07>>; 08<<; 09<<; 09>>; 08>>; 10<<; 10>>; 11<<; 11>>; 12<<; 12>>; 13<<; 13>>; 14<<; 14>>; 15<<; 15>>; 16<<; 16>>; 17<<; 17>>; 18<<; 18>>; 19<<; 19>>; 20<<; 20>>; 21<<; 21>>; 23<<; 23>>; 22<<; 22>>; 24<<; 24>>; 25<<; 25>>; 26<<; 26>>; 27<<; 27>>; 28<<; 28>>; 29<<; 29>>; 30<<; 30>>; 32<<; 32>>; 31<<; 31>>; 33<<; 33>>; 34<<; 34>>; 35<<; 35>>; 36<<; 36>>; 37<<; 37>>; 38<<; 38>>; 39<<; 39>>; 41>>; 40>>; 42>>; 43>>; 44>>; 45>>; 46>>; 47>>; 48>>; 49>>; 50>>; 51>>; 52>>; 53>>; 54>>; 55>>; 56>>; 57>>; 58>>; 59>>; 60>>; 61>>; 62>>; 63>>; 64>>; 65>>; 66>>; 67>>; 68>>; 69>>; 70>>; 71>>; 72>>; 73>>; 74>>; 75>>; 76>>; 77>>; 78>>; 79>>; 80>>; 81>>; 82>>; 83>>; 84>>; 85>>; 86>>; 87>>; 88>>; 89>>; 90>>; 91>>; 92>>; 93>>; 94>>; 95>>; 96>>; 97>>; 98>>; 99>>; 40<<; 41<<; 42<<; 43<<; 44<<; 45<<; 46<<; 47<<; 48<<; 49<<; 50<<; 51<<; 52<<; 53<<; 54<<; 55<<; 56<<; 57<<; 58<<; 59<<; 60<<; 
+00<<; 00>>; 01<<; 01>>; 02<<; 02>>; 03<<; 03>>; 04<<; 04>>; 05<<; 05>>; 06<<; 06>>; 07<<; 07>>; 08<<; 09<<; 09>>; 08>>; 10<<; 10>>; 11<<; 11>>; 12<<; 12>>; 13<<; 13>>; 14<<; 14>>; 15<<; 15>>; 16<<; 16>>; 17<<; 17>>; 18<<; 18>>; 19<<; 19>>; 20<<; 20>>; 21<<; 21>>; 23<<; 23>>; 22<<; 22>>; 24<<; 24>>; 25<<; 25>>; 26<<; 26>>; 27<<; 27>>; 28<<; 28>>; 29<<; 29>>; 30<<; 30>>; 32<<; 32>>; 31<<; 31>>; 33<<; 33>>; 34<<; 34>>; 35<<; 35>>; 36<<; 36>>; 37<<; 37>>; 38<<; 38>>; 39<<; 39>>; 41>>; 40>>; 42>>; 43>>; 44>>; 45>>; 46>>; 47>>; 48>>; 49>>; 50>>; 51>>; 52>>; 53>>; 54>>; 55>>; 56>>; 57>>; 58>>; 59>>; 60>>; 61>>; 62>>; 63>>; 64>>; 65>>; 66>>; 67>>; 68>>; 69>>; 70>>; 71>>; 72>>; 73>>; 74>>; 75>>; 76>>; 77>>; 78>>; 79>>; 80>>; 81>>; 82>>; 83>>; 84>>; 85>>; 86>>; 87>>; 88>>; 89>>; 90>>; 91>>; 92>>; 93>>; 94>>; 95>>; 96>>; 97>>; 98>>; 99>>; 40<<; 41<<; 42<<; 43<<; 44<<; 45<<; 46<<; 47<<; 48<<; 49<<; 50<<; 51<<; 52<<; 53<<; 54<<; 55<<; 56<<; 57<<; 58<<; 59<<; 60<<;
  (28527|1) client finished successfully..
-61<<; 62<<; 63<<; 64<<; 65<<; 66<<; 67<<; 68<<; 69<<; 70<<; 71<<; 72<<; 73<<; 74<<; 75<<; 76<<; 77<<; 78<<; 79<<; 80<<; 81<<; 82<<; 83<<; 84<<; 85<<; 86<<; 87<<; 88<<; 89<<; 90<<; 91<<; 92<<; 93<<; 94<<; 95<<; 96<<; 97<<; 98<<; 99<<; 
+61<<; 62<<; 63<<; 64<<; 65<<; 66<<; 67<<; 68<<; 69<<; 70<<; 71<<; 72<<; 73<<; 74<<; 75<<; 76<<; 77<<; 78<<; 79<<; 80<<; 81<<; 82<<; 83<<; 84<<; 85<<; 86<<; 87<<; 88<<; 89<<; 90<<; 91<<; 92<<; 93<<; 94<<; 95<<; 96<<; 97<<; 98<<; 99<<;
  (28526|1) server finished successfully..
 
 _Expected regression result_:
diff --git a/TAO/orbsvcs/tests/Bug_3387_Regression/README b/TAO/orbsvcs/tests/Bug_3387_Regression/README
index 46dcd2331b8..f85c922f5d2 100644
--- a/TAO/orbsvcs/tests/Bug_3387_Regression/README
+++ b/TAO/orbsvcs/tests/Bug_3387_Regression/README
@@ -1,7 +1,6 @@
-Event Notification Service
-
+$Id$
 
-File: Bug_3387_Regression test
+Event Notification Service
 
 This directory contains a test for this bug.
 
@@ -13,7 +12,7 @@ EndPoint, this can occur on embedded system or with ORBEndPoint, and
 after connecting, disconnectes then, after rebooting or re-running,
 comes back and tries to reconnect.  With the bug, the new consumer
 receives no events.  After fixing the bug the consumer will again
-receive events.  
+receive events.
 
 All of the special edge conditions are duplicated in the test.
 
diff --git a/TAO/orbsvcs/tests/LoadBalancing/GenericFactory/DeadMemberDetection_Inf_Ctrl/README b/TAO/orbsvcs/tests/LoadBalancing/GenericFactory/DeadMemberDetection_Inf_Ctrl/README
index e00f2d1a726..b510dd44279 100755
--- a/TAO/orbsvcs/tests/LoadBalancing/GenericFactory/DeadMemberDetection_Inf_Ctrl/README
+++ b/TAO/orbsvcs/tests/LoadBalancing/GenericFactory/DeadMemberDetection_Inf_Ctrl/README
@@ -1,81 +1,83 @@
+$Id$
+
 This program tests dead member detection feature on Load Balancer.
 The group uses infrastructure controlled membership. Three factories
-(servers) are created and added to the object group. The client use 
+(servers) are created and added to the object group. The client use
 the group object reference to make invocations.
 
 The test covers 4 test cases.
 
 1) Dead Member Detection with Round Robin Strategy
 
-   a. Invoke get_string(), the server 1 is active and picked to 
-      handle request. 
+   a. Invoke get_string(), the server 1 is active and picked to
+      handle request.
       Invoke exit () to crash server 1.
    b. Invoke exit () on crash server 2.
    c. Invoke get_string(), the server 3 is picked to handle request.
       Invoke exit () to crash server 3.
-   d. Invoke get_string(), no active member so client gets OBJECT_NOT_EXIST 
+   d. Invoke get_string(), no active member so client gets OBJECT_NOT_EXIST
       exception.
-     
+
 2) Hang Member Detection with Round Robin Strategy
 
-   a. Invoke get_string(), the server 1 is active and picked to 
-      handle request. 
+   a. Invoke get_string(), the server 1 is active and picked to
+      handle request.
       Invoke exit () to crash server 1.
    b. Invoke get_string(), liveliness check on server 2 and it timed
-      out on RECV because _non_existent implementation on server side 
-      has a delay to similate a hang server. The server 2 is still 
-      picked. The client request may be delayed but it should still 
+      out on RECV because _non_existent implementation on server side
+      has a delay to similate a hang server. The server 2 is still
+      picked. The client request may be delayed but it should still
       get reply. Invoke exit on the server 2 and the LB may detect
       it's lost.
-   c. Invoke get_string(), the server 3 is active and picked to 
-      handle request. 
+   c. Invoke get_string(), the server 3 is active and picked to
+      handle request.
       Invoke exit () to crash server 3.
-   c. Invoke get_string(), if LB has detected server 2 lost then 
+   c. Invoke get_string(), if LB has detected server 2 lost then
       client should get OBJECT_NOT_EXIST exception. If not detected
       it will return server 2 reference and the client invocation
       may get COMM_FAILURE or TRANSIENT exception.
 
 3) Dead Member Detection with Random Strategy
 
-   a. Invoke get_string(), a random server (e.g. 2) is active and picked to 
-      handle request. 
+   a. Invoke get_string(), a random server (e.g. 2) is active and picked to
+      handle request.
       Invoke exit () to crash the server.
-   b. Invoke get_string(), a random server (e.g. 1) except server picked in 
+   b. Invoke get_string(), a random server (e.g. 1) except server picked in
       step a) is picked to handle request.
       Invoke exit () to crash the server.
    c. Invoke get_string(), the last server (e.g. 3) is active and picked to
       handle request.
       Invoke exit () to crash the server.
-   d. Invoke get_string(), no active member so client gets OBJECT_NOT_EXIST 
+   d. Invoke get_string(), no active member so client gets OBJECT_NOT_EXIST
       exception.
 
 4) Hang Member Detection with Random Strategy
 
-   a. Invoke get_string(), a random server (e.g. 1) is active and picked to 
-      handle request. 
+   a. Invoke get_string(), a random server (e.g. 1) is active and picked to
+      handle request.
       Invoke exit () to crash the server.
-   b. Invoke get_string(), a random server (e.g. 2) except server picked in 
-      step a) is picked. Even the server 2 times out on liveliness check 
+   b. Invoke get_string(), a random server (e.g. 2) except server picked in
+      step a) is picked. Even the server 2 times out on liveliness check
       because of the delay in _non_existent implementation, it can still be
-      picked. The client request may be delayed but it should finally 
+      picked. The client request may be delayed but it should finally
       complete.
       Invoke exit () to crash the server.
    c. Invoke get_string(), the server not picked (e.g. 3) will be picked
       and client get reply from the server.
       Invoke exit () to crash the server.
-   c. Invoke get_string(), if LB has detected server 2 lost then 
+   c. Invoke get_string(), if LB has detected server 2 lost then
       client should get OBJECT_NOT_EXIST exception. If not detected
       it will return server 2 reference and the client invocation
       may get COMM_FAILURE or TRANSIENT exception.
 
-	
+
 To run the test use the run_test.pl script:
 
 $ ./run_test.pl
 
 	The script returns 0 if the test was successful and each test case
 	should print out "test passed.".
-	
-	
-	
+
+
+
 
diff --git a/TAO/orbsvcs/tests/LoadBalancing/LoadMonitor/CPU/README b/TAO/orbsvcs/tests/LoadBalancing/LoadMonitor/CPU/README
index ee845ff6081..6ce01e03a7f 100644
--- a/TAO/orbsvcs/tests/LoadBalancing/LoadMonitor/CPU/README
+++ b/TAO/orbsvcs/tests/LoadBalancing/LoadMonitor/CPU/README
@@ -1,11 +1,11 @@
-# $Id$
+$Id$
 
 This test verifies that Cygnus' CPU load monitor is working correctly.
 Run the test using the `run_test.pl' Perl script.  The expected test
 output is the following:
 
 ==== Running CPU Load Monitor test
- 
+
 Retrieving loads from LoadManager ...... DONE
 Retrieving loads directly from LoadMonitor ... DONE
 CPU Load Monitor test passed.