[
https://issues.apache.org/jira/browse/TS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905607#action_12905607
]
Leif Hedstrom commented on TS-55:
---------------------------------
How about we leave "emergency" and "fatal" with SE, and the rest we change to
"E" only. Thoughts?
> Logging: Default settings for diagnostic logging
> ------------------------------------------------
>
> Key: TS-55
> URL: https://issues.apache.org/jira/browse/TS-55
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.0.0a
> Environment: All platforms
> Reporter: George Paul
> Assignee: George Paul
> Priority: Minor
> Fix For: 2.1.3
>
>
> Currently the default diagnostic logging settings are as follows in
> proxy/mgmt2/RecordsConfig.cc :
> # O stdout
>
>
> # E stderr
>
>
> # S syslog
>
>
> # L diags.log
>
>
>
> proxy.config.diags.output.diag E
> proxy.config.diags.output.debug E
> proxy.config.diags.output.status S
> proxy.config.diags.output.note S
> proxy.config.diags.output.warning S
> proxy.config.diags.output.error SE
> proxy.config.diags.output.fatal SE
> proxy.config.diags.output.alert SE
> proxy.config.diags.output.emergency SE
> This means regular diagnostics will be logged to syslogd. It has been
> suggested that syslog logging be disabled due to syslogd locking up the
> system under heavy load. Instead by default and all diagnostic output go to
> stderr(E) where the output can be captured by TrafficCop in 'traffic.out'. A
> new configuration could possibly look like this:
> proxy.config.diags.output.diag E
> proxy.config.diags.output.debug E
> proxy.config.diags.output.status E
> proxy.config.diags.output.note E
> proxy.config.diags.output.warning E
> proxy.config.diags.output.error E
> proxy.config.diags.output.fatal E
> proxy.config.diags.output.alert E
> proxy.config.diags.output.emergency E
> -George
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
