[logback-dev] [JIRA] Commented: (LBCORE-147) RollingPolicy MaxHistory not deleting old files
Ceki Gulcu (JIRA)
noreply-jira at qos.ch
Thu Aug 25 22:10:16 CEST 2011
[ http://jira.qos.ch/browse/LBCORE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12094#action_12094 ]
Ceki Gulcu commented on LBCORE-147:
1) Rollover is triggered by the first LoggingEvent occurring subsequent to the begging of a new rollover period. Logback assumes that at least one LoggingEvent is generated per rollover period as the case where no LoggingEvent occurs in a period is highly unlikely (for any period duration over an hour).
2) I had a similar thought. However, the value of Q is independent of the length of the rollover period, is it not?
4) I'd like to avoid exposing a new parameter to the user unless there is a good need for it.
5) Creating a thread may be actually slower than deleting 20 local files. Files over the network is a different matter.
> RollingPolicy MaxHistory not deleting old files
> Key: LBCORE-147
> URL: http://jira.qos.ch/browse/LBCORE-147
> Project: logback-core
> Issue Type: Bug
> Components: Rolling
> Affects Versions: 0.9.18
> Environment: linux 2.6.18 64bits apache-tomcat-6.0.20 java/jre1.6.0_18
> Reporter: Rafael Diaz Maurin
> Assignee: Ceki Gulcu
> Attachments: TimeBasedRollingWithArchiveRemovalTest.java
> The MaxHistory does not do the trick : the old files are not deleted at all :
> cat logging.xml
> <appender name="IDP_ACCESS" class="ch.qos.logback.core.rolling.RollingFileAppender">
> <RollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
> <layout class="ch.qos.logback.classic.PatternLayout">
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the logback-dev