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

[sartak at bestpractical.com]

Author: sartak
Date: Wed May  6 16:27:57 2009
New Revision: 19477

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

Log:
LogToSyslog is also ignored and removed

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:27:57 2009
@@ -668,7 +668,7 @@
 
 =over 4
 
-=item C<$LogToSyslog>, C<$LogToScreen>
+=item C<$LogToScreen>
 
 The minimum level error that will be logged to the specific device.
 From lowest to highest priority, the levels are:
@@ -676,7 +676,6 @@
 
 =cut
 
-set($LogToSyslog    , 'info');
 set($LogToScreen    , 'info');
 
 =item C<$LogToFile>, C<$LogToFileNamed>
@@ -695,18 +694,6 @@
 set($LogToFile      , undef);
 set($LogToFileNamed , "rt.log");    #log to rt.log
 
-=item C<@LogToSyslogConf>
-
-On Solaris or UnixWare, set to ( socket => 'inet' ).  Options here
-override any other options RT passes to L<Log::Dispatch::Syslog>.
-Other interesting flags include facility and logopt.  (See the
-L<Log::Dispatch::Syslog> documentation for more information.)  (Maybe
-ident too, if you have multiple RT installations.)
-
-=cut
-
-set(@LogToSyslogConf, ());
-
 =item C<$StatementLog>,
 
 RT has rudimentary SQL statement logging support if you have

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:27:57 2009
@@ -81,7 +81,6 @@
     config_set( '$Databasename', db_name() );
 
     # generic logging
-    config_set( '$LogToSyslog',    undef );
     config_set( '$LogToScreen',    'error' );
     config_set( '$LogStackTraces', 'crit' );