felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Ström (Issue Comment Edited) (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Edited] (FELIX-2852) Infinite reloading of config file ending with .config
Date Tue, 21 Feb 2012 13:34:34 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212579#comment-13212579
] 

Johan Ström edited comment on FELIX-2852 at 2/21/12 1:33 PM:
-------------------------------------------------------------

~1 year later; is there any update on this bug? I still have this problem running 3.1.10 (as
shipped with Apache Karaf 2.2.5). As 3.1.10 is the latest version released, and the workaround
doesn't work on the released version, I'd say this is a problem. Patching trunk manually isn't
too production-friendly.
                
      was (Author: jstrom):
    ~1 year later; is there any update on this bug? I still have this problem running 3.1.10
(as shipped with Apache Karaf 2.2.5)
                  
> Infinite reloading of config file ending with .config
> -----------------------------------------------------
>
>                 Key: FELIX-2852
>                 URL: https://issues.apache.org/jira/browse/FELIX-2852
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>    Affects Versions: fileinstall-3.1.10
>            Reporter: Carl Hall
>            Priority: Critical
>         Attachments: felix-2852.diff
>
>
> When a config file ending with .config is written back to the file system, lastModified
is updated even if the file has not changed since it was last written/read. Config files ending
with .cfg are not affected by this as lastModified is not updated if the file has not changed.
> Workaround: apply the patch from FELIX-2843 and set felix.fileinstall.disableConfigSave=false

--
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

       

Mime
View raw message