[
https://issues.apache.org/jira/browse/KARAF-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132651#comment-13132651
]
Sergey Zhemzhitsky commented on KARAF-955:
------------------------------------------
Hello Guillaume,
Thanks for clarification.
Is it possible to make karaf read etc/ folder on startup and reinitialize
configurations which contain felix.fileinstall.filename property?
> Confusing behavior of ConfigAdmin
> ---------------------------------
>
> Key: KARAF-955
> URL: https://issues.apache.org/jira/browse/KARAF-955
> Project: Karaf
> Issue Type: Bug
> Components: karaf-config
> Affects Versions: 2.2.4
> Reporter: Sergey Zhemzhitsky
>
> Hi there,
> I've faced with the following behavior of ConfigAdmin which I suppose is a
> little bit confusing.
> Steps to reproduce:
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # *karaf.log* file should be there
> # Stop Karaf
> # Go to *$\{karaf.home}/data/log* directory and delete *karaf.log* file
> # When Karaf is stopped change *log4j.appender.out.file* property in the
> *$\{karaf.home}/etc/org.ops4j.pax.logging.cfg* file from
> *$\{karaf.data}/log/karaf.log* to *$\{karaf.data}/log/karaf1.log*
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # Only *karaf1.log* file is expected to be there, but empty *karaf.log* that
> has been deleted on the step 4 is also there.
--
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
