[Rt-commit] r19485 - in rt/3.999/branches/config-in-db: etc
sunnavy at bestpractical.com
sunnavy at bestpractical.com
Wed May 6 22:16:42 EDT 2009
Author: sunnavy
Date: Wed May 6 22:16:41 2009
New Revision: 19485
Modified:
rt/3.999/branches/config-in-db/etc/initialdata
rt/3.999/branches/config-in-db/lib/RT/Config.pm
Log:
remove log part from rt config
Modified: rt/3.999/branches/config-in-db/etc/initialdata
==============================================================================
--- rt/3.999/branches/config-in-db/etc/initialdata (original)
+++ rt/3.999/branches/config-in-db/etc/initialdata Wed May 6 22:16:41 2009
@@ -705,13 +705,6 @@
'inactive_status' => [ 'resolved', 'rejected', 'deleted' ],
'lexicon_languages' => ['*'],
'link_transactions_run1_scrip' => 0,
- 'log_dir' => '',
- 'log_stack_traces' => '',
- 'log_to_file' => undef,
- 'log_to_file_named' => 'rt.log',
- 'log_to_screen' => 'info',
- 'log_to_syslog' => 'info',
- 'log_to_syslog_conf' => [],
'logo_url' => '{{web_images_url}}bplogo.gif',
'loops_to_rt_owner' => 1,
'mail_command' => 'sendmailpipe',
@@ -756,7 +749,6 @@
'standalone_max_spare_servers' => 0,
'standalone_min_servers' => 1,
'standalone_min_spare_servers' => 0,
- 'statement_log' => undef,
'store_loops' => undef,
'strict_link_acl' => 1,
'suppress_inline_text_files' => undef,
Modified: rt/3.999/branches/config-in-db/lib/RT/Config.pm
==============================================================================
--- rt/3.999/branches/config-in-db/lib/RT/Config.pm (original)
+++ rt/3.999/branches/config-in-db/lib/RT/Config.pm Wed May 6 22:16:41 2009
@@ -444,7 +444,7 @@
=over 4
-=item C<gnu_pg>
+=item C<gnupg>
Set C<outgoing_messages_format> to 'inline' to use inline encryption and
signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format.
@@ -478,64 +478,6 @@
=back
-=head1 Logging
-
-The default is to log anything except debugging
-information to syslog. Check the L<Log::Dispatch> POD for
-information about how to get things by syslog, mail or anything
-else, get debugging info in the log, etc.
-
-It might generally make sense to send error and higher by email to
-some administrator. If you do this, be careful that this email
-isn't sent to this RT instance. Mail loops will generate a critical
-log message.
-
-=over 4
-
-=item C<log_to_syslog>, C<log_to_screen>
-
-The minimum level error that will be logged to the specific device.
-From lowest to highest priority, the levels are:
- debug info notice warning error critical alert emergency
-
-default: C<'info'>
-
-=item C<log_to_file>, C<log_dir>, C<log_to_file_named>
-
-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.
-
-default:
-log_to_file => C<undef>
-log_to_dir => C<''>
-log_to_file_named => C<"rt.log">
-
-=item C<log_to_syslog_conf>
-
-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.)
-
-default: C<[]>
-
-=item C<statement_log>,
-
-RT has rudimentary SQL statement logging support if you have
-DBIx-SearchBuilder 1.31_1 or higher; simply set C<statement_log> to be
-the level that you wish SQL statements to be logged at.
-
-default: C<undef>
-
-=back
-
=head1 Web Interface
=over 4
More information about the Rt-commit
mailing list