Hi, You can always "programmatically" update the org.ops4j.pax.logging configuration via ConfigAdmin service.
Just add the corresponding configuration as you would do "by hand". It's what log:set is doing for instance. It's also what ssh is doing changing level of a logger. Regards JB On 07/06/2019 15:12, jochenw wrote: > Thanks for the quick reply, JB! > > I've already seen your blog entry, and also know about the PaxAppender. > However, as far as I understood, for both I still need a configuration in > org.ops4j.pax.logging.cfg - e.g. the type RollingRandomAccessFile, the size > per file and the number of files in the policies, the file name, pattern > etc., or the name of the logger using that appender. > > For the PaxAppender solution, it is of course possible to have a self-made > writer, using some RollingFileWriter library. > > I'd be perfectly happy with delegating the configuration to pax-logging, but > currently I cannot see how to do that from code, without changing the > content of the org.ops4j.pax.logging.cfg or the respective PID. Maybe there > just is no simple solution like a "ConfigurationBuilder" replacement in > pax-logging. > > Regards > Jochen > > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
