[Prev] Thread [Next]  |  [Prev] Date [Next]

[jira] [Commented] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files. Joshua Masek (Commented) (JIRA) Thu Apr 05 09:01:34 2012


Joshua Masek commented on LOG4NET-27:

What I originally submitted (and looks like it has been made into a patch), I 
have been running in production for close to 3 years (against the 1.2.10 
version), and am not aware of any issues with it.  Seems to be working, and 
nobody has had a harddisk fill up with logs (and I log heavily).
I don't know if there are any concerns that have prevented it being in the 
trunk.  My guess is that development on log4net has been minimal (considering 
it took 5 years to have a new minor version release), and may have something to 
do with this.  Also in my opinion, it isn't simple to resolve cleanly (I did my 
best) and maybe there is still thought to be put into it.
What I provided wasn't necessarily even me recommending it to be in the trunk, 
but rather just something people could use to get around the limitation.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
For more information on JIRA, see: http://www.atlassian.com/software/jira