karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Troy Waldrep (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-798) Support for relocating karaf.history file
Date Thu, 11 Aug 2011 00:15:34 GMT

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

Troy Waldrep commented on KARAF-798:

Yeah, that would work as well.  All we're looking for is a clean way to handle the use case.

> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message