You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by maggu2810 <ma...@gmail.com> on 2015/02/09 11:23:41 UTC
Karaf: writable / read only directories
Hello,
the following thread implies, that there should be a separation between
directories a write access is needed and the read only data that is packaged
by distribution packages.
http://karaf.922171.n3.nabble.com/using-KARAF-HOME-BASE-vars-tp4031255p4031257.html
ATM I realized that there are multiple stuff that is written to:
- the directory 'data' is created
- the directory 'instances' is created
- the file 'lock' is created
- the file 'etc/config.properties' is modified (Generated command shutdown;
karaf.shutdown.command = ...)
So can I manage a clean separation between read only and read writable data.
As stated in the linked post 'etc' should be read only, so it could
distributed by the package maintainer.
Could I prevent the generation of the karaf.shutdown.command (to that file).
If the file is read only, karaf will not start.
--
View this message in context: http://karaf.922171.n3.nabble.com/Karaf-writable-read-only-directories-tp4038406.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Karaf: writable / read only directories
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
I created a Jira about that (about the config.properties update), and
have env variables for all.
Regards
JB
On 02/09/2015 11:23 AM, maggu2810 wrote:
> Hello,
>
> the following thread implies, that there should be a separation between
> directories a write access is needed and the read only data that is packaged
> by distribution packages.
> http://karaf.922171.n3.nabble.com/using-KARAF-HOME-BASE-vars-tp4031255p4031257.html
>
> ATM I realized that there are multiple stuff that is written to:
> - the directory 'data' is created
> - the directory 'instances' is created
> - the file 'lock' is created
> - the file 'etc/config.properties' is modified (Generated command shutdown;
> karaf.shutdown.command = ...)
>
> So can I manage a clean separation between read only and read writable data.
>
> As stated in the linked post 'etc' should be read only, so it could
> distributed by the package maintainer.
> Could I prevent the generation of the karaf.shutdown.command (to that file).
> If the file is read only, karaf will not start.
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Karaf-writable-read-only-directories-tp4038406.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com