karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-798) Support for relocating karaf.history file
Date Wed, 07 Mar 2012 14:18:59 GMT

     [ https://issues.apache.org/jira/browse/KARAF-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jamie goodyear updated KARAF-798:

    Fix Version/s:     (was: 3.0.0)

Bumping to 3.1.0 - if we gain a consensus for how we want to approach the relocatable history
file then we may bring this back to 3.0.0 to fix.
> 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
>             Fix For: 2.2.6, 3.1.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


View raw message