Thu Oct 6 11:56:19 UTC 2011 Marcel Smit <msmit@remedy.nl>

        * README:
        * examples/Connection/non_blocking/README:
        * examples/IPC_SAP/DEV_SAP/README:
        * examples/IPC_SAP/SOCK_SAP/README:
        * examples/IPC_SAP/SSL_SAP/README:
        * examples/Log_Msg/Log_Msg_MFC/README:
        * examples/Log_Msg/README:
        * examples/Logger/README:
        * examples/README:
        * examples/Reactor/Ntalker/README:
        * examples/Reactor/README:
        * examples/Reactor/TP_Reactor/README:
        * examples/Service_Configurator/Misc/README:
        * examples/Synch/README:
        * examples/System_V_IPC/README:
        * examples/Timer_Queue/README:
          Fuzz: trailing whitespaces, tab characters and ID strings

2 files changed, 45 insertions, 43 deletions

diff --git a/ACE/examples/Log_Msg/Log_Msg_MFC/README b/ACE/examples/Log_Msg/Log_Msg_MFC/README
index d64001aff87..8d6d12675c8 100644
--- a/ACE/examples/Log_Msg/Log_Msg_MFC/README
+++ b/ACE/examples/Log_Msg/Log_Msg_MFC/README
@@ -1,7 +1,9 @@
+$Id$
+
                      MFC Logging Example documentation
                      =================================
                             by Craig Rodrigues <crodrigu@bbn.com>
-		               2002/08/02
+                    2002/08/02
 
 The example in this directory is a Microsoft Foundation Class (MFC)
 example which illustrates how to write an ACE_Log_Msg_Callback which
diff --git a/ACE/examples/Log_Msg/README b/ACE/examples/Log_Msg/README
index 31da025a03d..b5344748e20 100644
--- a/ACE/examples/Log_Msg/README
+++ b/ACE/examples/Log_Msg/README
@@ -12,56 +12,56 @@ Log_Msg class to record various information.
           use-cases of ACE_Log_Msg please see the
           $ACE_ROOT/netsvcs/clients/Logger/ examples.
 
-	* test_log_msg.cpp: This program tests various feature of the
+  * test_log_msg.cpp: This program tests various feature of the
           Log_Msg facility.  It opens a log file and writes some
           messages using different log priorities and output stream.
 
-	  You can invoke the program with or without command
-	  parameters.  When invoked with any parameters like,
+    You can invoke the program with or without command
+    parameters.  When invoked with any parameters like,
 
-		./Log_Msg foobar
+    ./Log_Msg foobar
+  
+    the log messages are direct to stdout (or, ostream in C++.)
+    In this case, the program simulates an error EWOULDBLOCK and
+    write an error log to stdout as,
 
-	  the log messages are direct to stdout (or, ostream in C++.)
-	  In this case, the program simulates an error EWOULDBLOCK and
-	  write an error log to stdout as,
+    would block
+    op_status and errnum work!
 
-		would block
-		op_status and errnum work!
+    When invoked without any parameters, except does the same
+    test as above but logs to default log stream "stderr," the
+    program also demonstrates logging messages/errors with
+    different priority and changing the logging destination.  A
+    sample output is,
 
-	  When invoked without any parameters, except does the same
-	  test as above but logs to default log stream "stderr," the
-	  program also demonstrates logging messages/errors with
-	  different priority and changing the logging destination.  A
-	  sample output is,
+      would block
+      op_status and errnum work!
+        3.141600,         hello = 10000
+        6.283200,         world = 20000
+        6.283200,         world = 20000
+        9.424800,         world = 30000
+      12.566400,         world = 40000
+      15.708000,         world = 50000
+      HEXDUMP 48 bytes
+      01 00 00 00 02 00 00 00  04 00 00 00 08 00 00 00   ................
+      10 00 00 00 20 00 00 00  40 00 00 00 80 00 00 00   .... ...@.......
+      00 01 00 00 00 02 00 00  00 04 00 00 00 08 00 00   ................
+      ./Log_Msg.EXE: (2710), badname: Function not implemented
 
-	    would block
-	    op_status and errnum work!
-	      3.141600,         hello = 10000
-	      6.283200,         world = 20000
-	      6.283200,         world = 20000
-	      9.424800,         world = 30000
-	     12.566400,         world = 40000
-	     15.708000,         world = 50000
-	    HEXDUMP 48 bytes
-	    01 00 00 00 02 00 00 00  04 00 00 00 08 00 00 00   ................
-	    10 00 00 00 20 00 00 00  40 00 00 00 80 00 00 00   .... ...@.......
-	    00 01 00 00 00 02 00 00  00 04 00 00 00 08 00 00   ................
-	    ./Log_Msg.EXE: (2710), badname: Function not implemented
+    In this test, there are two lines containing "world` =
+    20000."  That's because in the program, both stderr and
+    stdout are "turned on" for logging before writing this log
+    message.  The line containing "world = 30000" is written to
+    stdout only.  Rest of the lines are all to the stderr.  You
+    can examine this behavior by redirecting stderr and stdout
+    to different files.
 
-	  In this test, there are two lines containing "world` =
-	  20000."  That's because in the program, both stderr and
-	  stdout are "turned on" for logging before writing this log
-	  message.  The line containing "world = 30000" is written to
-	  stdout only.  Rest of the lines are all to the stderr.  You
-	  can examine this behavior by redirecting stderr and stdout
-	  to different files.
+    The HEXDUMP output shows how to take an arbitrary object and
+    hexdump its content for debugging.  Finally, the program
+    shows an ordinary use case of logging error messages using
+    the ACE_ERROR macro.
 
-	  The HEXDUMP output shows how to take an arbitrary object and
-	  hexdump its content for debugging.  Finally, the program
-	  shows an ordinary use case of logging error messages using
-	  the ACE_ERROR macro.
-
-	  If you look into the program, there is also a demonstration
-	  showing how to disable certain priorities of error message
-	  temporarily.
+    If you look into the program, there is also a demonstration
+    showing how to disable certain priorities of error message
+    temporarily.