[
https://issues.apache.org/jira/browse/KARAF-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569746#comment-13569746
]
Jean-Baptiste Onofré edited comment on KARAF-2146 at 2/3/13 10:15 AM:
----------------------------------------------------------------------
I think that the patch is too restrictive:: it logs directly into the log file.
I would prefer to leverage pax-logging service to delegate the logging to the
service. Like this, log:display will render the messages and the user can
change the appenders (file, syslog, jdbc, ...).
was (Author: jbonofre):
I think that the patch is to restrictive:: it logs directly into the log
file.
I would prefer to leverage pax-logging service to delegate the logging to the
service. Like this, log:display will render the messages and the user can
change the appenders (file, syslog, jdbc, ...).
> Add a log command to log from shell to the log
> ----------------------------------------------
>
> Key: KARAF-2146
> URL: https://issues.apache.org/jira/browse/KARAF-2146
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
> Affects Versions: 2.3.0
> Reporter: Claus Ibsen
> Priority: Minor
> Attachments: KARAF-2146.patch.txt
>
>
> When working with Karaf, you often have to look in the logs etc. And
> sometimes you need to configure the logs to be very verbose with TRACE level
> logging.
> It would be nice if I from the shell could do
> {code}
> log:log "I am going to stop bundle 88 now, and you can find this text in the
> log. Yeah coffee is great."
> {code}
> eg to log at INFO level a text. This makes it easier to grep in the log after
> this text. To find a spot you wanna look at. If the log is very verbose and
> has many many lines. It takes longer to find the spot.
--
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
