Fuzz

13 files changed, 79 insertions, 61 deletions

diff --git a/ACE/examples/ASX/Event_Server/README b/ACE/examples/ASX/Event_Server/README
index 6038355a53e..2ed942618a3 100644
--- a/ACE/examples/ASX/Event_Server/README
+++ b/ACE/examples/ASX/Event_Server/README
@@ -1,3 +1,5 @@
+$Id$
+
 This subdirectory illustrates a number of the ACE ASX framework
 features using an ACE_Stream application called the Event Server.  For
 more information on the design and use of the ACE ASX framework please
@@ -22,7 +24,7 @@ The Event Server example works as follows:
    # Consumer
    % transceiver -p 10002 -h hostname -C
 
-   or 
+   or
 
    # Supplier
    % transceiver -p 10003 -h hostname -S
@@ -35,13 +37,13 @@ The Event Server example works as follows:
    Consumer(s) and Supplier(s) in different windows to make it easier
    to understand the output.
 
-3. Once the Consumer(s) and Supplier(s) are connected, you can 
+3. Once the Consumer(s) and Supplier(s) are connected, you can
    type data from any Supplier window.  This data will be routed
    through the Modules/Tasks in the event_server's Stream and be
    forwarded to the Consumer(s).
 
    Since the transceivers are full-duplex you can also send messages
-   from the Consumer(s) to Supplier(s).  However, the Event Server will 
+   from the Consumer(s) to Supplier(s).  However, the Event Server will
    warn you about this since it's not really kosher to have Consumers
    sending to Suppliers...
 
@@ -65,15 +67,15 @@ Some of the more interesting things to add would be:
    of the Event_Server based on messages it got from Suppliers
    (or Consumers).
 
-3. Support for "pull" operations, as well as "push" operations. 
+3. Support for "pull" operations, as well as "push" operations.
    This would basically involve adding a "MIB Module" to get/set
    the "values" associated with "names" passed in by Peers.  This
    could probably replace the Event_Analysis Module.
 
 4. Filtering and correlation (this should probably be done
-   via a separate Module that handles filtering and correlation). 
+   via a separate Module that handles filtering and correlation).
 
-5. More flexible concurrency model(s), e.g., "Active Object per-Consumer".  
+5. More flexible concurrency model(s), e.g., "Active Object per-Consumer".
    This would enable the Event Server process to handle flow control
    more gracefully than it does not (it currently "hangs," which isn't
    desirable).
diff --git a/ACE/examples/ConfigViewer/README b/ACE/examples/ConfigViewer/README
index 1f83c2dc848..66ac158aff8 100644
--- a/ACE/examples/ConfigViewer/README
+++ b/ACE/examples/ConfigViewer/README
@@ -1,17 +1,19 @@
+$Id$
+
 Configuration Viewer 1.0
 ========================
 
-This is something I quickly threw together to allow GUI editing of 
+This is something I quickly threw together to allow GUI editing of
 ACE_Configuration files.  I thought it would be useful and serve as a
 better example of how to use ACE_Configuration.  I developed this under
 Windows 2000, but it should easily port to any platform that wxWindows
-supports (see http://www.wxwindows.org.).  
+supports (see http://www.wxwindows.org.).
 
 ==============
    Usage
 ==============
 All functionality is delivered through the file menu and right mouse button
-context menus.  The file menu lets you create the different types of 
+context menus.  The file menu lets you create the different types of
 ACE_Configurations such as a transient heap, persistent heap or Win32
 Registry heap.  A new persistent heap may be created, or an older one
 may be opened.  The win32 registry will require you to enter the path
@@ -23,7 +25,7 @@ may import or export entries from a heap to an INI file using the
 Import/Export file commands.
 
 The right mouse button opens up a context menu in both the tree control
-and the list control.  
+and the list control.
 From the tree context menu, you can:
 1) Create new keys (these hold name/value pairs)
 2) Create new string values
@@ -46,7 +48,7 @@ Known Bugs/Issues:
 *) The entire configuration file is loaded into the tree when it is opened.
    For large configurations, this may take a while.  A good improvement
    would be to load items as the user expands them.
-*) At the time of this writing, there is a nasty bug in 
+*) At the time of this writing, there is a nasty bug in
    ACE_Configuration_Heap that has to do with changing the value
    of an existing entry.  I have submitted a patch to fix this, but
    it may not go in until 5.1.3 (current version is 5.1.2).  I strongly
diff --git a/ACE/examples/Connection/blocking/README b/ACE/examples/Connection/blocking/README
index c7763e3ed04..c347901a010 100644
--- a/ACE/examples/Connection/blocking/README
+++ b/ACE/examples/Connection/blocking/README
@@ -1,3 +1,5 @@
+$Id$
+
 Presently, this directory contains only one example application for
 SPIPEs.  The test source code is contained in SPIPE-acceptor.h and
 SPIPE-connector.h.
@@ -29,7 +31,7 @@ hello
 starting up daemon test_sock_connector
 Opening acepipe
 activating 5
- 
+
 please enter input..: hello
 
 There are a number of other options that you can provide.  Please see
diff --git a/ACE/examples/DLL/README b/ACE/examples/DLL/README
index 3526af927a9..2414c6a7a81 100644
--- a/ACE/examples/DLL/README
+++ b/ACE/examples/DLL/README
@@ -15,7 +15,7 @@ objects like Newsweek and Today deriving form it. The libraries are
 dynamically linked on demand.  Thus, they can be changed on the fly
 and accessed with its new changes.
 
-The ACE_DLL class used in this example is an helper class for 
+The ACE_DLL class used in this example is an helper class for
 performing various operations on the library object.
 
 Compilation and Execution:
@@ -39,7 +39,7 @@ Compilation and Execution:
    Load DLL.sln which contains DLL_Main.vcproj, DLL_Today.vcproj and DLL_Newsweek.vcproj.
 
    Build each vcproj such that you build DLL_Main.vcproj last.
-   This is because the test_dll.exe will be using Today.dll and Newsweek.dll. 
+   This is because the test_dll.exe will be using Today.dll and Newsweek.dll.
 
    Execute test_dll
 
diff --git a/ACE/examples/IOStream/README b/ACE/examples/IOStream/README
index ab215fc779d..80ce2e68b94 100644
--- a/ACE/examples/IOStream/README
+++ b/ACE/examples/IOStream/README
@@ -1,3 +1,5 @@
+$Id$
+
 This example illustrates the use of the ACE_IOStream and
 ACE_Streambuf_T templates to create an object based on ACE_*_Stream
 classes.  These classes provide C++ iostream functionality across a
@@ -7,7 +9,7 @@ To run the tests simply build the executables in the client and server
 directories and then do the following in separate windows:
 
 # Window 1
-% server/iostream_server 
+% server/iostream_server
 (10049) starting up daemon
 
 # Window 2
diff --git a/ACE/examples/Logger/README b/ACE/examples/Logger/README
index bac9aa1d127..7e8840e7d07 100644
--- a/ACE/examples/Logger/README
+++ b/ACE/examples/Logger/README
@@ -1,3 +1,5 @@
+$Id$
+
 This directory contains a simple client/server implementation of the
 distributed logging server described in several papers in the C++
 Report (which can be obtained via the following WWW URLs:
@@ -9,7 +11,7 @@ The example consists of the following directories:
 
 		This program talks directly to the server logging
 		daemon.  The server daemon must be started before you
-		can run this test. 
+		can run this test.
 
 	. simple-server
 
@@ -26,7 +28,7 @@ The example consists of the following directories:
 To see a more complex solution that implements the design described in
 the C++ Report articles, please see the:
 
-$ACE_ROOT/netsvcs/{clients,lib,servers} 
+$ACE_ROOT/netsvcs/{clients,lib,servers}
 
 directories.
 
diff --git a/ACE/examples/OS/Process/README b/ACE/examples/OS/Process/README
index c22757eb73f..62df0c1698b 100644
--- a/ACE/examples/OS/Process/README
+++ b/ACE/examples/OS/Process/README
@@ -1,3 +1,5 @@
+$Id$
+
 This directory contains two examples: <imore> and <process>.  They
 show how you can play with various features of ACE_Process to create
 new processes.
@@ -19,7 +21,7 @@ portably specify path, command-line arguments, environment variable
 values.  It also allows applications to set the new process' standard
 handles (stdin, stdout, and stderr).  ACE_Process is created with the
 ACE_Process_Options and can be used to perform operations on the
-running process.  
+running process.
 
 Notice that this example uses NT version's UNIX utilities like
 "DATE.EXE," and "ls.exe."  You can find where to get them from
diff --git a/ACE/examples/QOS/Change_Receiver_FlowSpec/README b/ACE/examples/QOS/Change_Receiver_FlowSpec/README
index 58320ef8def..3ce38205c8c 100644
--- a/ACE/examples/QOS/Change_Receiver_FlowSpec/README
+++ b/ACE/examples/QOS/Change_Receiver_FlowSpec/README
@@ -1,6 +1,6 @@
 $Id$
 
-A Regression test for ACE QoS features. 
+A Regression test for ACE QoS features.
 ---------------------------------------
 
 This test implements a simple Receiver-Sender program that ensures
@@ -8,7 +8,7 @@ Quality of Service (QoS) guarantees on the underlying network before
 transmitting data. The program tests the ACE QoS APIs/features. The
 test works for Winsock2 APIs on Win2K as well as RAPI on Solaris.
 
-In addition it dynamically changes the receiver flow spec which in 
+In addition it dynamically changes the receiver flow spec which in
 turn changes the RESV messages sent.
 
 
@@ -19,11 +19,11 @@ Build Requirements :
 --------------------
 1. Two Win2K machines.
 2. June98 Platform SDK or later.
-3. Link with ws2_32.lib 
+3. Link with ws2_32.lib
 
 The test consists of a server (which is the receiver) and a client
- (which is the sender). 
- 
+ (which is the sender).
+
  The receiver is started first (though it is not mandatory) as :
 
  server -m merengue.cs.wustl.edu:9091
@@ -60,7 +60,7 @@ On Win2K the user must have administrative access to the machine to
 run this program.  It seems to be a pre-requisite to opening QoS
 sockets.
 
-The sender and receiver should be run on different Win2K machines. 
+The sender and receiver should be run on different Win2K machines.
 
 The test demonstrates how to GQOS enable an application using the ACE QoS APIs.
 It concentrates on the use of various ACE QoS APIs and their correctness.
@@ -79,8 +79,8 @@ PLATFORM_RAPI_LDFLAGS += -L/project/doc/vishal/rapi/rel4.2a4/rsvpd/
 
 assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
 
-1. Compile ACE with 
-       
+1. Compile ACE with
+
    make rapi=1 static_libs_only=1
 
    Static library option is used because the RAPI library that we have
@@ -107,7 +107,7 @@ assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
        sender beguine/6000 [ t 2000000 100000 2000000 512 1024 ]
 
    From Macarena:
-       wait until done with ACE 
+       wait until done with ACE
        dest udp macarena/5000          <session name>
        reserve wf [ cl 2000000 100000 2000000 512 1024 ]
 
@@ -118,7 +118,7 @@ assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
    that rtap session is released on both machines.
 
 -------------------------------------------------------------------------------
-  
+
 If you run into any problems with this test please contact Vishal
 Kachroo <vishal@cs.wustl.edu>.
 
diff --git a/ACE/examples/QOS/Change_Sender_TSpec/README b/ACE/examples/QOS/Change_Sender_TSpec/README
index a8423774320..75f10545047 100644
--- a/ACE/examples/QOS/Change_Sender_TSpec/README
+++ b/ACE/examples/QOS/Change_Sender_TSpec/README
@@ -1,6 +1,6 @@
 $Id$
 
-A Regression test for ACE QoS features. 
+A Regression test for ACE QoS features.
 ---------------------------------------
 
 This test implements a simple Receiver-Sender program that ensures
@@ -8,7 +8,7 @@ Quality of Service (QoS) guarantees on the underlying network before
 transmitting data. The program tests the ACE QoS APIs/features. The
 test works for Winsock2 APIs on Win2K as well as RAPI on Solaris.
 
-In addition it dynamically changes the sender TSpec which in turn 
+In addition it dynamically changes the sender TSpec which in turn
 changes the PATH messages.
 
 ------------------------------------------------------------------------
@@ -18,11 +18,11 @@ Build Requirements :
 --------------------
 1. Two Win2K machines.
 2. June98 Platform SDK or later.
-3. Link with ws2_32.lib 
+3. Link with ws2_32.lib
 
 The test consists of a server (which is the receiver) and a client
- (which is the sender). 
- 
+ (which is the sender).
+
  The receiver is started first (though it is not mandatory) as :
 
  server -m merengue.cs.wustl.edu:9091
@@ -59,7 +59,7 @@ On Win2K the user must have administrative access to the machine to
 run this program.  It seems to be a pre-requisite to opening QoS
 sockets.
 
-The sender and receiver should be run on different Win2K machines. 
+The sender and receiver should be run on different Win2K machines.
 
 The test demonstrates how to GQOS enable an application using the ACE QoS APIs.
 It concentrates on the use of various ACE QoS APIs and their correctness.
@@ -78,8 +78,8 @@ PLATFORM_RAPI_LDFLAGS += -L/project/doc/vishal/rapi/rel4.2a4/rsvpd/
 
 assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
 
-1. Compile ACE with 
-       
+1. Compile ACE with
+
    make rapi=1 static_libs_only=1
 
    Static library option is used because the RAPI library that we have
@@ -106,7 +106,7 @@ assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
        sender beguine/6000 [ t 2000000 100000 2000000 512 1024 ]
 
    From Macarena:
-       wait until done with ACE 
+       wait until done with ACE
        dest udp macarena/5000          <session name>
        reserve wf [ cl 2000000 100000 2000000 512 1024 ]
 
@@ -117,7 +117,7 @@ assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
    that rtap session is released on both machines.
 
 -------------------------------------------------------------------------------
-  
+
 If you run into any problems with this test please contact Vishal
 Kachroo <vishal@cs.wustl.edu>.
 
diff --git a/ACE/examples/QOS/Diffserv/README b/ACE/examples/QOS/Diffserv/README
index 285d514ad12..3b0866a1356 100644
--- a/ACE/examples/QOS/Diffserv/README
+++ b/ACE/examples/QOS/Diffserv/README
@@ -1,3 +1,5 @@
+$Id$
+
 This directory contains an example which
 tests the setting of the Diffserv Codepoint (DSCP)
 values in the
@@ -6,7 +8,7 @@ IP TOS field of a stream of UDP packets.
 Running the example
 ===================
 
-(1)  On one host, run: 
+(1)  On one host, run:
         server [UDP port number]
 
      If port number is omitted, a default port number of 20002
@@ -29,7 +31,7 @@ Running the example
 
 Introduction
 ============
-In RFC 2474, the Type of Service (TOS) field in 
+In RFC 2474, the Type of Service (TOS) field in
 the IP header was renamed the Diffserv (DS) field.
 The DS field is one octet (8 bits).
 
@@ -98,7 +100,7 @@ RFC 2597, "Assured Forwarding PHB Group", http://www.ietf.org/rfc/rfc2597.txt
 
 RFC 3246, "An Expedited Forwarding PHB", http://www.ietf.org/rfc/rfc3246.txt
 
-RFC 3247, "Supplemental Information for the New Definition of the EF PHB", 
+RFC 3247, "Supplemental Information for the New Definition of the EF PHB",
           http://www.ietf.org/rfc/rfc3247.txt
 
 RFC 3168, "The Addition of Explicit Congestion Notification (ECN)
diff --git a/ACE/examples/QOS/Simple/README b/ACE/examples/QOS/Simple/README
index 13255842932..6c084472e3d 100644
--- a/ACE/examples/QOS/Simple/README
+++ b/ACE/examples/QOS/Simple/README
@@ -1,6 +1,6 @@
-//$Id$
+$Id$
 
-A Regression test for ACE QoS features. 
+A Regression test for ACE QoS features.
 ---------------------------------------
 
 This test implements a simple Receiver-Sender program that ensures
@@ -16,10 +16,10 @@ Build Requirements :
 --------------------
 1. Two Win2K machines.
 2. June98 Platform SDK or later.
-3. Link with ws2_32.lib 
+3. Link with ws2_32.lib
+
+The test consists of a receiver and a sender.
 
-The test consists of a receiver and a sender. 
- 
  The sender is started first (though it is not mandatory) as :
 
  sender -m merengue.cs.wustl.edu:9091 -P 10004
@@ -36,7 +36,7 @@ The test consists of a receiver and a sender.
 
 The sample Sender is started next as :
 
-  receiver -m merengue.cs.wustl.edu:9091 
+  receiver -m merengue.cs.wustl.edu:9091
 
  -m: specifies the multicast session address that both client and
      server subscribe to for QoS events.
@@ -56,7 +56,7 @@ On Win2K the user must have administrative access to the machine to
 run this program.  It seems to be a pre-requisite to opening QoS
 sockets.
 
-The sender and receiver should be run on different Win2K machines. 
+The sender and receiver should be run on different Win2K machines.
 
 The test demonstrates how to GQOS enable an application using the ACE QoS APIs.
 It concentrates on the use of various ACE QoS APIs and their correctness.
@@ -75,9 +75,9 @@ PLATFORM_RAPI_LDFLAGS += -L/project/doc/vishal/rapi/rel4.2a4/rsvpd/
 
 assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
 
-1. Compile ACE with 
-       
-   make rapi=1 
+1. Compile ACE with
+
+   make rapi=1
 
 2. Run the RSVP Daemon on two machines: (merengue.cs and macarena.cs)
 
@@ -98,8 +98,8 @@ assuming that RAPI library is installed in /project/doc/vishal/rapi/rel4.2a4/
    RESV, PATH and other RSVP messages, run the QoS example, making sure
    that rtap session is released on both machines.
 
-The test consists of a receiver and a sender. 
- 
+The test consists of a receiver and a sender.
+
  The sender is started first (though it is not mandatory) as :
 
  sender -m macarena.cs.wustl.edu:9091 -P 10004
@@ -116,7 +116,7 @@ The test consists of a receiver and a sender.
 
 The sample Sender is started next as :
 
-  receiver -m macarena.cs.wustl.edu:9091 
+  receiver -m macarena.cs.wustl.edu:9091
 
  -m: specifies the multicast session address that both client and
      server subscribe to for QoS events.
@@ -133,7 +133,7 @@ The sample Sender is started next as :
  -h: Displays the help on various options.
 
 -------------------------------------------------------------------------------
-  
+
 If you run into any problems with this test please contact Vishal
 Kachroo <vishal@cs.wustl.edu>.
 
diff --git a/ACE/examples/Reactor/Multicast/README b/ACE/examples/Reactor/Multicast/README
index 85f64cc8120..d82ebd059f5 100644
--- a/ACE/examples/Reactor/Multicast/README
+++ b/ACE/examples/Reactor/Multicast/README
@@ -1,12 +1,14 @@
+$Id$
+
 The following test illustrates the SOCK Mcast multicast wrappers in
 conjunction with the Reactor.  This test was written by Tim Harrison
 (harrison@cs.wustl.edu).
 
-To run the server type: 
+To run the server type:
 
 % server &
 
-It will wait for the first message sent to it and then read for 5 seconds. 
+It will wait for the first message sent to it and then read for 5 seconds.
 
 To run the client type any of these:
 
diff --git a/ACE/examples/Web_Crawler/README b/ACE/examples/Web_Crawler/README
index 4f81809173d..2892f3bc367 100644
--- a/ACE/examples/Web_Crawler/README
+++ b/ACE/examples/Web_Crawler/README
@@ -1,11 +1,13 @@
+$Id$
+
 Web Crawler                                     Kirthika Parameswaran
 -----------
 
 The Web Crawler follows the  HTTP_1.1 protocol.
- 
+
 This Crawler crawls in  either FIFO or LIFO order over the URLs
-now stored in a ACE_Unbounded_Queue. The Command Processor pattern is 
-used in this example. 
+now stored in a ACE_Unbounded_Queue. The Command Processor pattern is
+used in this example.
 
 Also the auto-purging feature where connections are removed from the cache
 when the process runs out of file descriptors, is added to this example.
@@ -16,7 +18,7 @@ Run:
 ---
 
 
-> make 
+> make
 
 > main -r -u www.cs.wustl.edu/~kirthika/test.html -o LIFO