Here it is: <?xml version="1.0" encoding="UTF-8" ?> <configuration scan="true"> <appender name="LOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/log/zeugma/selectterms/selectterms.log </file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>/var/log/zeugma/selectterms/selectterms.%d{yyyy-MM-dd}.log.gz</FileNamePattern> <MaxHistory>30</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger - %msg%n</Pattern> </layout> </appender> <root level="info"> <appender-ref ref="LOG" /> </root> </configuration> -- Stephen Duncan Jr www.stephenduncanjr.com On Tue, Sep 15, 2009 at 9:02 AM, Ceki Gulcu <ceki@qos.ch> wrote:
Hi Stephen,
Thank you for this information. Logback has test cases for this situation (roll over in presence of start/stop). It appears that they did not catch the problem. Would it be possible for you to post your logback configuration file so that I can reproduce the problem?
TIA,
Stephen Duncan Jr wrote:
Thanks. I verified that reverting my projects last night to 0.9.16 did fix it so that those cron-scheduled apps did roll-over the log file when run again this morning.
-Stephen
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user