Yes, just tried that. Didn't work. Below is the relevant section of the
org.ops4j.pax.logging.cfg file. None of it seems to affect the log file
contents, though it is sent to the file name specified.
log4j.logger.org.apache.karaf.main=WARN
log4j.logger.org.apache.karaf.main.SimpleFileLock=WARN
# Root logger - default level was INFO
log4j.rootLogger=WARN, osgi:*
log4j.throwableRenderer=org.apache.log4j.OsgiThrowableRenderer
log4j.appender.out.threshold=WARN
# File appender
log4j.appender.out=org.apache.log4j.RollingFileAppender
log4j.appender.out.layout=org.apache.log4j.PatternLayout
log4j.appender.out.layout.ConversionPattern=%d{ISO8601} | %-5.5p | %-16.16t
| %-32.32c{1} | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n
log4j.appender.out.file=${karaf.data}/log/karaf.log
log4j.appender.out.append=true
log4j.appender.out.maxFileSize=1MB
log4j.appender.out.maxBackupIndex=10
--
View this message in context:
http://karaf.922171.n3.nabble.com/Loggin-in-cluster-can-t-be-configured-tp4040207p4040211.html
Sent from the Karaf - User mailing list archive at Nabble.com.
