Fixed fuzz

8 files changed, 39 insertions, 53 deletions

diff --git a/TAO/performance-tests/Cubit/TAO/DII_Cubit/README b/TAO/performance-tests/Cubit/TAO/DII_Cubit/README
index c73482bdf76..3d0488f5504 100644
--- a/TAO/performance-tests/Cubit/TAO/DII_Cubit/README
+++ b/TAO/performance-tests/Cubit/TAO/DII_Cubit/README
@@ -1,8 +1,8 @@
-// $Id$
+$Id$
 
-This is the cubit example that does everything using DII requests. 
+This is the cubit example that does everything using DII requests.
 It uses the server in IDL_Cubit. Getting a reference
-to the Cubit object, making the Cubit operation calls, 
+to the Cubit object, making the Cubit operation calls,
 and shutting down the server are all done with DII requests.
 
 NOTES: The IDL_Cubit server used to run a Naming Service so the client
@@ -15,8 +15,8 @@ To run the tests with one "button-push", execute the perl script run_test.pl
 in this directory. It will start up the server and client. The client will
 shut down the server when the tests are finished.
 
-If you want to run each executable separately and manually, run the 
-server first (in IDL_Cubit). Then run the client with zero or more of 
+If you want to run each executable separately and manually, run the
+server first (in IDL_Cubit). Then run the client with zero or more of
 the following args:
 
         [-d]                 Increments TAO_debug_level. It's additive, up
@@ -26,15 +26,15 @@ the following args:
 
         [-i <factory IOR>]   For passing the IOR by hand.
 
-        [-f <filename>]      If server is run with [-o <filename>] option, 
+        [-f <filename>]      If server is run with [-o <filename>] option,
                              it outputs its factory IOR to a file, which
                              the client can read with this option.
 
         [-x]                 Shuts down server when finished.
 
-If using the -i option, you might want to run the server with the option 
-[-ORBobjrefstyle url]. This will cause the server to display its IOR in a 
-more human-readable form. The server can be run in the same window in the 
+If using the -i option, you might want to run the server with the option
+[-ORBobjrefstyle url]. This will cause the server to display its IOR in a
+more human-readable form. The server can be run in the same window in the
 background, or in a different window.
 
 The command line options, default calls per loop, order and display
diff --git a/TAO/performance-tests/Cubit/TAO/IDL_Cubit/README b/TAO/performance-tests/Cubit/TAO/IDL_Cubit/README
index cd3c6535bd5..d5421161407 100644
--- a/TAO/performance-tests/Cubit/TAO/IDL_Cubit/README
+++ b/TAO/performance-tests/Cubit/TAO/IDL_Cubit/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
 
 This example uses the TAO IDL compiler to generate the SII stubs and
 skeletons.  You can either run the server in the background in the
diff --git a/TAO/performance-tests/Cubit/TAO/MT_Cubit/README b/TAO/performance-tests/Cubit/TAO/MT_Cubit/README
index 6a9a0ff666c..1f4caa60143 100644
--- a/TAO/performance-tests/Cubit/TAO/MT_Cubit/README
+++ b/TAO/performance-tests/Cubit/TAO/MT_Cubit/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
 
 THE MT_CUBIT EXAMPLE
 --------------------
@@ -115,10 +115,10 @@ by the client.
 
         Default Value: Disabled
 
-[-u <seconds>] runs the client/server utilization test for a number of <requests>.  
-        The output is the number of seconds for the test to make such number of requests.  
+[-u <seconds>] runs the client/server utilization test for a number of <requests>.
+        The output is the number of seconds for the test to make such number of requests.
         Now run the same test but with the -l option to make the same number of requests,
-        this time not using CORBA, instead directly making function calls.  The difference 
+        this time not using CORBA, instead directly making function calls.  The difference
         in time for each test to make the same number of requests is the utilization of
         the OS/ORB combined.
      (Note: This option overrides any specified "-t" option)
@@ -193,13 +193,13 @@ for ALL.
 server:
 ------
 $rsh host_name arun path_to_server -e iiop://DOTTED_DECIMAL_ADDRESS:0
- -f path_to_ior_file -ORBDottedDecimalAddresses 1 <server_options> 
+ -f path_to_ior_file -ORBDottedDecimalAddresses 1 <server_options>
 
 Since Chorus doesn't support DNS, you should pass
 dotted_decimal_address of the server machine to -e option.
 
 You DONT have to use -ORBDottedDecimalAddresses 1 if you have
-TAO_USE_DOTTED_DECIMAL_ADDRESSES defined in your config.h file. 
+TAO_USE_DOTTED_DECIMAL_ADDRESSES defined in your config.h file.
 
 e.g
 $rsh tambora1 arun /MT_Cubit/server -e iiop://128.252.165.82:0 -f /ior
diff --git a/TAO/performance-tests/Cubit/TAO/README b/TAO/performance-tests/Cubit/TAO/README
index 61da08408de..7be940f726d 100644
--- a/TAO/performance-tests/Cubit/TAO/README
+++ b/TAO/performance-tests/Cubit/TAO/README
@@ -1,3 +1,5 @@
+$Id$
+
 There are three versions of the Cubit example. Individual README files
 in the respective directories explain these versions in further
 detail.
@@ -7,12 +9,12 @@ detail.
                  Cubit example with tao_idl compiler generated stubs
                  and skeletons
 
-        . MT_Cubit 
+        . MT_Cubit
 
 		 Multithreaded real-time Cubit example.
 
         . DII_Cubit
-                
+
                  Cubit example with hand-generated stubs.  When
                  TAO supports the DII interface this will
                  illustrate how it works.
diff --git a/TAO/performance-tests/POA/Demux/README b/TAO/performance-tests/POA/Demux/README
index c0bcaf94755..4f43d7c2a82 100644
--- a/TAO/performance-tests/POA/Demux/README
+++ b/TAO/performance-tests/POA/Demux/README
@@ -1,18 +1,4 @@
-// $Id$
-// ============================================================================
-//
-// = LIBRARY
-//    TAO/performance-tests/Demux
-//
-// = FILENAME
-//    README
-//
-// = AUTHOR
-//
-//    Aniruddha Gokhale
-//
-// ============================================================================
-
+$Id$
 
 This test directory tests various demultiplexing strategies used in
 TAO for POA, object, and operation name lookups
@@ -29,7 +15,7 @@ demux_test_client.{h, cpp}: Client-side implementation details
 demux_test_macros.h: Some constants used by both the client and the server
 
 
-Generated Files: 
+Generated Files:
 ----------------
 
 Must run ./CodeGen/demux tool to generate the following files. See
@@ -63,7 +49,7 @@ client -d  (for debugging)
 
 
 ------
-*NOTE* 
+*NOTE*
 ------
 The num_POAs, num_objs, and num_ops must match on the client
 and server side.
@@ -84,13 +70,13 @@ Make the following changes in Object_Adapter.cpp :
 
 #define ACE_ENABLE_TIMEPROBES
 
-Comment out all ACE_FUNCTION_TIMEPROBE calls except the one 
+Comment out all ACE_FUNCTION_TIMEPROBE calls except the one
 in  locate_poa  ACE_FUNCTION_TIMEPROBE
 (TAO_OBJECT_ADAPTER_FIND_POA_START);
 
 
 In the demux_test_client : The object loop increments by one.
-In gen_names.cpp : 
+In gen_names.cpp :
 > Codegen/demux -p 25
 > make
 > ./server -p 25
diff --git a/TAO/performance-tests/POA/README b/TAO/performance-tests/POA/README
index af00cf0d727..3b36d35e4c0 100644
--- a/TAO/performance-tests/POA/README
+++ b/TAO/performance-tests/POA/README
@@ -1,6 +1,6 @@
-// $Id$
+$Id$
 
-The following applications are used to measure performance of TAO's POA. 
+The following applications are used to measure performance of TAO's POA.
 
         . Object_Creation_And_Registration
 
diff --git a/TAO/performance-tests/README b/TAO/performance-tests/README
index 1fbf7af6fe8..88b025d2088 100644
--- a/TAO/performance-tests/README
+++ b/TAO/performance-tests/README
@@ -1,6 +1,4 @@
-#
 # $Id$
-#
 
 This directory contains a number of tests that illustrate the
 performance of TAO and other ORBs.  The individual directories contain
@@ -18,14 +16,14 @@ READMEs on how to run the following performance tests:
           and jitter.
 
         . POA
-        
+
           Various tests of the TAO's POA performance.
 
         . Pluggable
 
           The tests in this directory time the latency contributed by
           various parts of the ORB, but mostly the emphasis is on the
-          contribution due to the pluggable protocols code.  
+          contribution due to the pluggable protocols code.
 
         . RTCorba
 
diff --git a/TAO/performance-tests/RTCorba/Oneways/Reliable/README b/TAO/performance-tests/RTCorba/Oneways/Reliable/README
index 69a29e8350d..c722c7b579f 100644
--- a/TAO/performance-tests/RTCorba/Oneways/Reliable/README
+++ b/TAO/performance-tests/RTCorba/Oneways/Reliable/README
@@ -1,4 +1,4 @@
-
+$Id$
 
 Server:
 
@@ -41,8 +41,8 @@ test type is anything else, the -m argument is not used. To get
 reasonable results with buffered oneway requests, it's a good idea
 to make the number of iterations -i a multiple of the queue size -m.
 This will insure that there are no requests left in the queue to be
-sent when the tests are done with their timings. For buffered 
-oneways, control is returned to the application as soon as the 
+sent when the tests are done with their timings. For buffered
+oneways, control is returned to the application as soon as the
 request is placed on the queue, or, if the queue is being flushed,
 as soon as all the requests are sent.
 
@@ -52,7 +52,7 @@ returned to the application when the request is handed off to the
 transport (usually TCP) layer.
 
 If the test type is 'server', control is returned to the application
-after any servant locator is called, but before the servant 
+after any servant locator is called, but before the servant
 executes the request. This will enable any location forwarding
 information to be returned to the client.
 
@@ -70,13 +70,13 @@ The -w option sets the number of empty loops of 1000 performed by
 the servant. To test the advantage of SYNC_WITH_SERVER over
 SYNC_WITH_TARGET and twoway requests, the servant must perform
 some 'significant' work that a oneway request with a SyncScope
-policy value of SYNC_WITH_SERVER does not wait on, while the 
+policy value of SYNC_WITH_SERVER does not wait on, while the
 other two types of requests mentioned above do.
 
 
-All the above command line options except -k, -s, -p and -x may be 
-used with the perl script run_test.pl. If no test type is specified, 
-the script will run each test type in turn before the server is shut 
+All the above command line options except -k, -s, -p and -x may be
+used with the perl script run_test.pl. If no test type is specified,
+the script will run each test type in turn before the server is shut
 down.
 
 There is also a perl script called client_test.pl, which facilitates
@@ -85,7 +85,7 @@ this script, first run the server manually, then run client_test.pl.
 With this script, the server will not shut down automatically.
 
 There is code in the test to set the priorities of the client and
-server threads to values consistent with a real time priority 
+server threads to values consistent with a real time priority
 class on Solaris and other Unix systems. If the user is not logged
 in as a superuser, a message will be output that the threads are
-running in a timesharing priority class.	
+running in a timesharing priority class.