karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Zurczak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-3654) Customize the logs location with KARAF_LOG
Date Fri, 10 Apr 2015 16:29:14 GMT

    [ https://issues.apache.org/jira/browse/KARAF-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14489886#comment-14489886

Vincent Zurczak commented on KARAF-3654:

Well, I will reply to myself.
I made the change, I added a KARAF_LOG variable. See https://github.com/vincent-zurczak/karaf/commit/2ec51999e7c5dce2003fb4571416eb7822720258

And it works. But after digging in the code and performing some manual tests, I came to the
conclusion that no matter where $KARAF_DATA points to, we can still specify the logs output
in the log4j configuration file.

It does not matter that all the scripts reference $KARAF_DATA/log.
If the log4j configuration points to another location, it will be picked up instead of the
default location.

So, basically, this JIRA entry is a waste of time. :P
Sorry about this, you can close it.

> Customize the logs location with KARAF_LOG
> ------------------------------------------
>                 Key: KARAF-3654
>                 URL: https://issues.apache.org/jira/browse/KARAF-3654
>             Project: Karaf
>          Issue Type: New Feature
>    Affects Versions: 4.0.0.M1, 4.0.0.M2
>            Reporter: Vincent Zurczak
>            Priority: Minor
> Hi,
> We have been working on creating a Debian package for one of our custom Karaf distributions.
And we would like to specify the location of the logs (under *var/log/...*). Unfortunately,
the logs location is tied to Karaf's data directory (KARAF_DATA).
> Few weeks ago, it was suggested to create a new variable called *KARAF_LOG*, default
to *$KARAF_DATA/log*. I think this is a good idea and that it should be implemented. See http://karaf.922171.n3.nabble.com/Configuring-location-of-log4j-out-files-td4038948.html
> PS: I have been working on this upgrade this afternoon. I will try to submit a patch
to discuss.

This message was sent by Atlassian JIRA

View raw message