Docs to go with SIGUSR[12] debugging patch

[Chip Seraphine]

Documentation patch to go with code patch at 
http://lists.gnu.org/archive/html/help-cfengine/2004-12/msg00102.html


--- cfengine-2.1.12.dist/doc/cfengine-Reference.texinfo    2004-11-22 
13:06:30.000000000 -0600
+++ cfengine-2.1.12.patched/doc/cfengine-Reference.texinfo    2005-01-19 
16:14:55.120491000 -0600
@@ -147,7 +147,8 @@
* Work directory::             
* Hard classes::               
* Evaluated classes and special functions:: 
-* Filenames and paths::        
+* Filenames and paths::
+* Debugging with signals::       
@end menu

@node Installation, Work directory, Reference introduction, Reference 
introduction
@@ -354,7 +355,7 @@
@c SECTION
@c 
-------------------------------------------------------------------------------

-@node Filenames and paths,  , Evaluated classes and special functions, 
Reference introduction
+@node Filenames and paths, Debugging with signals, Evaluated classes 
and special functions, Reference introduction
@section Filenames and paths

Filenames in Unix-like operating systems
@@ -401,6 +402,22 @@
Paths beginning with a backslash are assumed to be win32 paths.  They
must begin with a drive letter or double-slash server name.

+@c 
-------------------------------------------------------------------------------
+@c SECTION
+@c 
-------------------------------------------------------------------------------
+
+@node Debugging with signals,  , Filenames and paths, Reference 
introduction
+@section Debugging with signals
+
+It is possible to turn debugging output on or off on a running 
cfagent.  This is
+useful for troubleshooting the cause of hangups, or for getting 
debugging output
+from a cfagent launched from cfexecd.
+
+A running cfagent process that receives a SIGUSR1 will immediately 
begin to behave
+as if it had been invoked with the '-d2' option.  A SIGUSR2 will cause 
a running
+cfagent to run as if the '-d2' option had not been invoked.
+
+Note that this output is often quite verbose.

@c **********************************************************************
@c CHAPTER



--

Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com

--- cfengine-2.1.12.dist/doc/cfengine-Reference.texinfo 2004-11-22 
13:06:30.000000000 -0600
+++ cfengine-2.1.12.patched/doc/cfengine-Reference.texinfo      2005-01-19 
16:14:55.120491000 -0600
@@ -147,7 +147,8 @@
 * Work directory::              
 * Hard classes::                
 * Evaluated classes and special functions::  
-* Filenames and paths::         
+* Filenames and paths::
+* Debugging with signals::        
 @end menu
 
 @node Installation, Work directory, Reference introduction, Reference 
introduction
@@ -354,7 +355,7 @@
 @c SECTION
 @c 
-------------------------------------------------------------------------------
 
-@node Filenames and paths,  , Evaluated classes and special functions, 
Reference introduction
+@node Filenames and paths, Debugging with signals, Evaluated classes and 
special functions, Reference introduction
 @section Filenames and paths
 
 Filenames in Unix-like operating systems
@@ -401,6 +402,22 @@
 Paths beginning with a backslash are assumed to be win32 paths.  They
 must begin with a drive letter or double-slash server name.
 
+@c 
-------------------------------------------------------------------------------
+@c SECTION
+@c 
-------------------------------------------------------------------------------
+
+@node Debugging with signals,  , Filenames and paths, Reference introduction
+@section Debugging with signals
+
+It is possible to turn debugging output on or off on a running cfagent.  This 
is
+useful for troubleshooting the cause of hangups, or for getting debugging 
output
+from a cfagent launched from cfexecd.
+
+A running cfagent process that receives a SIGUSR1 will immediately begin to 
behave
+as if it had been invoked with the '-d2' option.  A SIGUSR2 will cause a 
running
+cfagent to run as if the '-d2' option had not been invoked. 
+
+Note that this output is often quite verbose.
 
 @c **********************************************************************
 @c CHAPTER