[Rt-commit] rt branch, 4.0/logging-config-docs, created. rt-4.0.1-265-ga774fd2

[Kevin Falcone]

The branch, 4.0/logging-config-docs has been created
        at  a774fd2c0bc3d7c3d3c891f616bbd865819dd74a (commit)

- Log -----------------------------------------------------------------
commit 7414b6463a24a5a26df21e29864191fede7dcac1
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Fri Aug 5 10:32:01 2011 -0400

    Remove some confusing language in LogToFile and spell out valid values
    
    Also talk about why you might not get your syslog messages and where to
    find logs from LogToScreen

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index cdfe938..4181812 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -228,6 +228,14 @@ From lowest to highest priority, the levels are:
 
     debug info notice warning error critical alert emergency
 
+Many syslogds are configured to discard or file debug messages away, so
+if you're attempting to debug RT you may need to reconfigure your
+syslogd or use one of the other logging options.
+
+Logging to your screen affects scripts run from the command line as well
+as the STDERR sent to your webserver (so these logs will usually show up
+in your web server's error logs).
+
 =cut
 
 Set($LogToSyslog, "info");
@@ -235,14 +243,16 @@ Set($LogToScreen, "info");
 
 =item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed>
 
-Logging to a standalone file is also possible, but note that the file
-should needs to both exist and be writable by all direct users of the
+Logging to a standalone file is also possible.  The file
+needs to both exist and be writable by all direct users of the
 RT API.  This generally includes the web server and whoever
 rt-crontool runs as.  Note that rt-mailgate and the RT CLI go through
 the webserver, so their users do not need to have write permissions to
 this file. If you expect to have multiple users of the direct API,
 Best Practical recommends using syslog instead of direct file logging.
 
+You should set C<$LogToFile> to one of the levels documented above.
+
 =cut
 
 Set($LogToFile, undef);

commit a774fd2c0bc3d7c3d3c891f616bbd865819dd74a
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Fri Aug 5 10:40:01 2011 -0400

    rewrap my rewording

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 4181812..613f589 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -243,13 +243,13 @@ Set($LogToScreen, "info");
 
 =item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed>
 
-Logging to a standalone file is also possible.  The file
-needs to both exist and be writable by all direct users of the
-RT API.  This generally includes the web server and whoever
-rt-crontool runs as.  Note that rt-mailgate and the RT CLI go through
-the webserver, so their users do not need to have write permissions to
-this file. If you expect to have multiple users of the direct API,
-Best Practical recommends using syslog instead of direct file logging.
+Logging to a standalone file is also possible. The file needs to both
+exist and be writable by all direct users of the RT API. This generally
+includes the web server and whoever rt-crontool runs as. Note that
+rt-mailgate and the RT CLI go through the webserver, so their users do
+not need to have write permissions to this file. If you expect to have
+multiple users of the direct API, Best Practical recommends using syslog
+instead of direct file logging.
 
 You should set C<$LogToFile> to one of the levels documented above.
 

-----------------------------------------------------------------------