Fixed fuzz

14 files changed, 38 insertions, 24 deletions

diff --git a/TAO/tests/AMI/README b/TAO/tests/AMI/README
index 04117a71d7d..40368fbdc4a 100644
--- a/TAO/tests/AMI/README
+++ b/TAO/tests/AMI/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 Description:
 This is a simple test for AMI callback model.
@@ -8,7 +8,7 @@ Use TAO_HAS_CORBA_MESSAGING
 and TAO_HAS_AMI_CALLBACK
 to compile TAO. This enables the AMI code in it.
 
-Use -GC on the TAO IDL compiler to generate code for AMI callbacks. 
+Use -GC on the TAO IDL compiler to generate code for AMI callbacks.
 
 Usage:
 =====
diff --git a/TAO/tests/Bug_1020_Basic_Regression/README b/TAO/tests/Bug_1020_Basic_Regression/README
index d20377f2685..586baa7bad0 100644
--- a/TAO/tests/Bug_1020_Basic_Regression/README
+++ b/TAO/tests/Bug_1020_Basic_Regression/README
@@ -1,11 +1,13 @@
 /**
 
+$Id$
+
 @page Bug_1020_Basic_Regression Test README File
 
 	The simplest possible test BUG 1020 regression for TAO.  This
 is a very simple test for TAO.
 
-        
+
         The test does the following
 
 - A server waits for a request from the client
@@ -19,13 +21,13 @@ is a very simple test for TAO.
   reference it got from the client.
 
 - The client threads after processing a few invocation abort, there by
-  crashing the client. 
+  crashing the client.
 
 - The server should survive the crash
 
 - The test passes sequence<octet> between client and server in either
   direction with the purpose of ensuring that the tranport gets flow
-  controlled. 
+  controlled.
 
 To run the test
 
diff --git a/TAO/tests/Bug_3647_Regression/README b/TAO/tests/Bug_3647_Regression/README
index 13afa51b826..30d662a2a15 100644
--- a/TAO/tests/Bug_3647_Regression/README
+++ b/TAO/tests/Bug_3647_Regression/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page Bug_3647_Regression Test README File
 
 This test demonstrates the problem described in bugzilla entry #3647.
@@ -7,7 +9,7 @@ This test demonstrates the problem described in bugzilla entry #3647.
 In this test we have three participants:
 
 A) A back-end server that will inconveniently block in the middle of
-   its work 
+   its work
 B) A middle-tier server that is trying to communicate with the back
    end server using SYNC_WITH_TRANSPORT oneway calls, with timeouts.
 C) A client application that is sending twoway calls to the
@@ -22,7 +24,7 @@ incoming requests from the client application.
 What we observe is that the middle-tier application blocks, but not in
 the event loop as it should, but while checking if the socket is ready
 for output.
-  
+
 To run the test use the run_test.pl script:
 
 $ ./run_test.pl
diff --git a/TAO/tests/Bug_3953_Regression/README b/TAO/tests/Bug_3953_Regression/README
index ab058d902f6..e71af6be668 100644
--- a/TAO/tests/Bug_3953_Regression/README
+++ b/TAO/tests/Bug_3953_Regression/README
@@ -1,4 +1,6 @@
-This is a test of the nested upcall feature in TAO using mt_noupcall. 
+$Id$
+
+This is a test of the nested upcall feature in TAO using mt_noupcall.
 start off by calling the server and providing a callback object and a
 time-to-live number.  The server will callback the client (using the
 callback object) and decrement the time-to-live number.
diff --git a/TAO/tests/File_IO/README b/TAO/tests/File_IO/README
index 1362696a08a..47c3d055f59 100644
--- a/TAO/tests/File_IO/README
+++ b/TAO/tests/File_IO/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page File_IO Test README File
 
 	A stress test for receiving large replies. The replies are
@@ -7,7 +9,7 @@
 	1002 to the surface. The test doesnt seem to have anything
 	special, but just to be sure that bug 1002 doesnt show up
 	again in some other form. This test was donated by Jonathan
-	Reis <reis@stentor.com>. 
+	Reis <reis@stentor.com>.
 
 	To run the test use the run_test.pl script:
 
diff --git a/TAO/tests/Forwarding/README b/TAO/tests/Forwarding/README
index 12c0bd3a90c..ff4ce9af985 100644
--- a/TAO/tests/Forwarding/README
+++ b/TAO/tests/Forwarding/README
@@ -25,6 +25,6 @@ $ ./run_test.pl
 @todo The test is not nearly a complete test for location forwarding,
       for example, it does not test deeeply nested location forwards
       or the interactions between location forwarding and multiple
-      profiles. 
+      profiles.
 
 */
diff --git a/TAO/tests/POA/EndpointPolicy/README b/TAO/tests/POA/EndpointPolicy/README
index e2d37c6e6e9..c0f92d32704 100644
--- a/TAO/tests/POA/EndpointPolicy/README
+++ b/TAO/tests/POA/EndpointPolicy/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page EndpointPolicy Test README File
 
   This test validates the TAO-specific Endpoint Policy. The Endpoint Policy
@@ -28,7 +30,7 @@ $ ./run_test.pl
 
   Beyond the basic test run using run_test.pl, there are two variants,
   a localhost based test and a "defaulted host" test. The localhost test
-  uses "localhost" as the hostname rather than allowing the server to 
+  uses "localhost" as the hostname rather than allowing the server to
   get the systems hostname. The Localhost test is not when autorunning
   on the vxworks platform.
 
@@ -36,7 +38,7 @@ $ ./run_test.pl
 
 $ ./run_test_lh.pl
 
-  In the defaulted host test, the hostname argument supplied to the 
+  In the defaulted host test, the hostname argument supplied to the
   endpoint policy is "". As discussed in Bug #3256, the behavior of
   using defaulted hosts is changed so that unless more than one
   protocol are involved, a defaulted hostname is not allowed in the
diff --git a/TAO/tests/POA/Generic_Servant/README b/TAO/tests/POA/Generic_Servant/README
index fd37775219e..de69d3bdd23 100644
--- a/TAO/tests/POA/Generic_Servant/README
+++ b/TAO/tests/POA/Generic_Servant/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
 
 Generic Servant:
 ===============
@@ -17,6 +17,6 @@ Typing
 
 creates an executable client and server library.
 
-To run the client, type 
+To run the client, type
 
 % client -k file://ior
diff --git a/TAO/tests/POA/Loader/README b/TAO/tests/POA/Loader/README
index db78c9c5df6..4edd1726efe 100644
--- a/TAO/tests/POA/Loader/README
+++ b/TAO/tests/POA/Loader/README
@@ -28,7 +28,7 @@ Object-to-Servant association is added to the Active Object Map
 maintained by the POA.  This association becomes invalid when the POA
 is destroyed or/and the Object is deactivated.  In contrast, for the
 Servant_Locator example operation request from the client causes the
-servant to be linked, processed, destroyed, and unlinked.  
+servant to be linked, processed, destroyed, and unlinked.
 
 For all examples, the dynamic configuration granularity is at the POA
 level,i.e., a Servant Activator or Servant Locator is associated with
@@ -57,4 +57,4 @@ example:
 
 The output will demonstrate the different actions performed by the
 Servant_Manager via the Servant_Activator and the Servant_Locator
-interfaces. 
+interfaces.
diff --git a/TAO/tests/POA/NewPOA/README b/TAO/tests/POA/NewPOA/README
index 347c22c8df2..3700fe4124b 100644
--- a/TAO/tests/POA/NewPOA/README
+++ b/TAO/tests/POA/NewPOA/README
@@ -1,3 +1,5 @@
+$Id$
+
 This application explains the usage scenario, where new POAs will have
 to be created.
 
@@ -8,8 +10,8 @@ Run this example as follows.
 Comments :
 =========
 
- - Creates the POA hierarchy as given in the header of the NewPOA.cpp 
+ - Creates the POA hierarchy as given in the header of the NewPOA.cpp
    file.
-        
+
  - Prints out names of all the POAs.
 
diff --git a/TAO/tests/POA/On_Demand_Activation/README b/TAO/tests/POA/On_Demand_Activation/README
index d5fbc21506c..56c7cdd24fd 100644
--- a/TAO/tests/POA/On_Demand_Activation/README
+++ b/TAO/tests/POA/On_Demand_Activation/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
 
 On_Demand_Activation Tests:
 ==========================
@@ -64,7 +64,7 @@ Servant Activator:
 
 2. Get the IOR for "first test"  from the server output .
 
-3. Run client -k IOR	
+3. Run client -k IOR
 
 4. You should get an output
 
diff --git a/TAO/tests/POA/On_Demand_Loading/README b/TAO/tests/POA/On_Demand_Loading/README
index 1e54111f6f9..56e45bd4ad7 100644
--- a/TAO/tests/POA/On_Demand_Loading/README
+++ b/TAO/tests/POA/On_Demand_Loading/README
@@ -53,5 +53,5 @@ interfaces.
 
 NOTE: If directly running run_test.pl srcipt then by default the example
 uses Generic_Servant as the servant. Hence its necessary to build
-$TAO_ROOT/examples/POA/Generic_Servant before you build and run this 
+$TAO_ROOT/examples/POA/Generic_Servant before you build and run this
 example.
diff --git a/TAO/tests/POA/POA_BiDir/README b/TAO/tests/POA/POA_BiDir/README
index 347c22c8df2..3700fe4124b 100644
--- a/TAO/tests/POA/POA_BiDir/README
+++ b/TAO/tests/POA/POA_BiDir/README
@@ -1,3 +1,5 @@
+$Id$
+
 This application explains the usage scenario, where new POAs will have
 to be created.
 
@@ -8,8 +10,8 @@ Run this example as follows.
 Comments :
 =========
 
- - Creates the POA hierarchy as given in the header of the NewPOA.cpp 
+ - Creates the POA hierarchy as given in the header of the NewPOA.cpp
    file.
-        
+
  - Prints out names of all the POAs.
 
diff --git a/TAO/tests/POA/Persistent_ID/README b/TAO/tests/POA/Persistent_ID/README
index 976de6c96e0..c7fb17322fa 100644
--- a/TAO/tests/POA/Persistent_ID/README
+++ b/TAO/tests/POA/Persistent_ID/README
@@ -1,7 +1,7 @@
 $Id$
 
 This test checks the combination of PERSISTENT & SYSTEM_ID POA
-policies. 
+policies.
 
 A servant is registered on the RootPOA. The client tells the server to
 create a POA with PERSISTENT & SYSTEM_ID policies.  The server does so