karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-798) Support for relocating karaf.history file
Date Mon, 12 Mar 2012 12:50:40 GMT

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

Jean-Baptiste Onofré commented on KARAF-798:
--------------------------------------------

    protected File getHistoryFile() {
        return new File(System.getProperty("karaf.history", new File(System.getProperty("user.home"),
".karaf/karaf.history").toString()));
    }

So, using -Dkaraf.history allows you to define the location of the history file (and it falls
back to .karaf/karaf.history in the user home if not defined).
                
> Support for relocating karaf.history file
> -----------------------------------------
>
>                 Key: KARAF-798
>                 URL: https://issues.apache.org/jira/browse/KARAF-798
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>            Reporter: Troy Waldrep
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.2.6, 3.0.0
>
>
> We have a servicemix-based product that has to perform a setuid to a lower-privileged
user while running on linux.  We've accounted for most permissions-based issues that result
from doing this by ensuring that the lower-privileged user has write access to the necessary
files under the data directory.
> Unfortunately, we can't do this with karaf.history since it is written to the home directory
of the user that started the stack (root in this case).  The lower-privileged usually doesn't
have *any* visibility into this directory, let alone write privileges.  If a configuration
option was provided to specify the location of the karaf.history file (or the option to not
even write or expect to find one), then we could treat this file like any other.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message