Done. https://issues.apache.org/jira/browse/FELIX-6519
Thanks JB! G On Tue, Apr 5, 2022 at 11:35 PM Jean-Baptiste Onofré <[email protected]> wrote: > Hi Greg, > > Yes, it's "normal". Let me explain. To avoid an infinite loop when you > are logged in via ssh, log:* commands (log:tail and log:display for > instance) are changing default org.ops4j.pax.logging configuration. > So, if the config files are read only, configadmin won't be able to update. > > It's something I did for 3.4.6 a while ago. > > However I can update the logic a bit to deal with the read only case. > > Do you mind creating a Jira about that ? > > Regards > JB > > Regards > JB > > On Tue, Apr 5, 2022 at 9:36 PM Greg Logan <[email protected]> wrote: > > > > Hi all, > > > > We are looking at upgrading from Karaf 3.4.3 to 3.4.6, and noticed an > odd behaviour. If your Karaf config files are read only (say, in a docker > container) and you try to run log:tail you get an immediate stack > trace[1]. Is this intended behaviour? It's not blocking our ability to > upgrade since it works fine 99% of the time, but it seems like odd > behaviour to me - especially since it doesn't happen in 3.4.3! > > > > Thanks, > > G > > > > 1: > https://github.com/opencast/opencast/pull/3542#issuecomment-1078458078 >
