[
https://issues.apache.org/jira/browse/WHIRR-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647618#comment-13647618
]
Graham Gear commented on WHIRR-722:
-----------------------------------
Sure Tom, uploaded new patch
[graham-patch-WHIRR-722-2.patch|https://issues.apache.org/jira/secure/attachment/12581529/graham-patch-WHIRR-722-2.patch]
addressing this.
Note that the '--quiet' option pre-dates my patch, but was only sparingly used
by the shipped plugins.
Please also note that the patched log4j-cli.xml culls all system logs from the
console and given most handlers dont print a lot to stdout, whirr will become
pretty quiet. For those plugins that do provide a lot of stdout user level
messages (eg whirr-cm) this is a much better situation and there is plenty of
'noise'. The log4j-cli.xml remains to be customised, so users who prefer the
combined system and user level console output can return the config if they
want.
> 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,
> graham-patch-WHIRR-722-2.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
