Instances will be configurable soon (it's based on KARAF_BASE).

The lock location can be changed using etc/system.properties:

karaf.lock.dir

else it uses KARAF_BASE.

Regards
JB

On 06/16/2015 01:13 PM, CLEMENT Jean-Philippe wrote:
I found there is a "instances" directory and a "lock" file which are created at 
runtime. On which base directory/env. variable are they created?

Regards,
JP

[@@ OPEN @@]


-----Message d'origine-----
De : Jean-Baptiste Onofré [mailto:[email protected]]
Envoyé : mardi 16 juin 2015 12:53
À : [email protected]
Objet : Re: Karaf installation to a read-only directory

Hi JP,

1/ KARAF_DATA has to be "writable"
2/ etc/system.properties has to be "writable" as it's where the shutdown 
command is added at first startup (it's not fixed in the meaning that it doesn't prevent 
the bootstrap) 3/ if you want to support update of config file (when using ConfigMBean or 
config:* commands), KARAF_ETC has to be writable

So, just provide KARAF_DATA variable in bin/karaf to a directory where you can 
write and it will work (eventually KARAF_ETC too).

Regards
JB

On 06/16/2015 12:05 PM, CLEMENT Jean-Philippe wrote:
Dear Karaf Team,

We would like to install Karaf in a directory which is read-only. By read-only 
I mean that no directory or file cannot be written at runtime inside the 
installation directory, so they must be located somewhere else.

What is the most simple way to achieve this?

Regards,
JP

PS: At present time we are using Karaf 3.0.2

[@@ OPEN @@]


--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com


--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to