[
https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728569#comment-14728569
]
Dominik Psenner commented on LOG4NET-27:
----------------------------------------
The solution is not as simple as it may look because it is computationally hard
to find the files that have been rolled away and thus it is computationally
hard to correctly calculate the maximum number of backup files. If you need a
maximum number of backup files, do not roll on datetime boundaries. This may be
solved with the reimplementation of the RollingFileAppender (LOG4NET-367), but
that again won't be happening any time soon. If you need this feature, best you
could do is get involved and continue the work on the reimplementation of the
RollingFileAppender.
Cheers
> Rolling files on date/time boundaries doesn't support a maximum number of
> backup files.
> ---------------------------------------------------------------------------------------
>
> Key: LOG4NET-27
> URL: https://issues.apache.org/jira/browse/LOG4NET-27
> Project: Log4net
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 1.2.11
> Reporter: Florian Ramillien
> Priority: Minor
> Fix For: 1.2 Maintenance Release
>
> Attachments: LOG4NET-27.patch, RollingFileAppender.cs,
> RollingFileAppender.cs, RollingFileAppender.cs, RollingFileAppender.cs.patch,
> RollingFileAppender.patch, RollingFileAppender.zip, appender_diff,
> rollingfileappender.diff
>
>
> A maximum of backup files exist when rolling files on file size, but not for
> rolling on date/time.
> This can be implemented with the same config key : MaxSizeRollBackups
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
