[Rt-commit] r19480 - in rt/3.999/trunk: lib/RT/Test

[sartak at bestpractical.com]

Author: sartak
Date: Wed May  6 16:36:47 2009
New Revision: 19480

Modified:
   rt/3.999/trunk/etc/RT_Config.pm
   rt/3.999/trunk/lib/RT/Test/Shredder.pm

Log:
LogToFile also gone

Modified: rt/3.999/trunk/etc/RT_Config.pm
==============================================================================
--- rt/3.999/trunk/etc/RT_Config.pm	(original)
+++ rt/3.999/trunk/etc/RT_Config.pm	Wed May  6 16:36:47 2009
@@ -678,21 +678,6 @@
 
 set($LogToScreen    , 'info');
 
-=item C<$LogToFile>
-
-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 RT API.  This generally include the web server, whoever
-rt-crontool runs as.  Note that as 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.
-
-=cut
-
-set($LogToFile      , undef);
-
 =back
 
 =head1 Web Interface Configuration

Modified: rt/3.999/trunk/lib/RT/Test/Shredder.pm
==============================================================================
--- rt/3.999/trunk/lib/RT/Test/Shredder.pm	(original)
+++ rt/3.999/trunk/lib/RT/Test/Shredder.pm	Wed May  6 16:36:47 2009
@@ -83,9 +83,6 @@
     # generic logging
     config_set( '$LogToScreen',    'error' );
     config_set( '$LogStackTraces', 'crit' );
-
-    # logging to standalone file
-    config_set( '$LogToFile', 'debug' );
 }
 
 =head3 config_set