whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Gear (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WHIRR-722) Improve user and system level logging capability
Date Thu, 02 May 2013 14:40:16 GMT

     [ https://issues.apache.org/jira/browse/WHIRR-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Graham Gear updated WHIRR-722:

    Attachment: graham-patch-WHIRR-722-1.patch
> Improve user and system level logging capability
> ------------------------------------------------
>                 Key: WHIRR-722
>                 URL: https://issues.apache.org/jira/browse/WHIRR-722
>             Project: Whirr
>          Issue Type: Improvement
>    Affects Versions: 0.8.2
>            Reporter: Graham Gear
>             Fix For: 0.8.3
>         Attachments: graham-patch-WHIRR-722-1.patch
> Currently the whirr infrastructure leverages log4j for system level logging and stdout/stderr
for user level. The former is configured via the 'conf/log4j-cli.xml', the latter via the
'--quiet' command line paramater.
> It is suggested that the default shipped log4j-cli.xml tune down (or preferable off)
its console logging, but remain logging to whirr.log.
> It is also suggested the '--quiet' command paramater be exposed to Handlers as well as
Commands, so that they can leverage it.
> In this way, user and system level logging can be delineated (ie console for user logging,
whirr.log for system) without each polluting the other.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message