[logback-user] Change FixedWindowRollingPolicy rolling behaviour

[David Roussel]

That seems reasonable, and it avoids the "too many renames" problem that the current strategy has. 

It would need additional logic to determine what index to start with at app startup time.  

Of course if you submit an initial implementation that would move things along. :-)

David

> On 13 May 2016, at 08:44, DK <desmond.kirrane at gmail.com> wrote:
> 
> Ok, maybe I'm missing something... but instead of reverse order could
> FixedWindowRollingPolicy maintain a 'currentIndex'
> 
> - It begins with currentIndex = 0
> - The active file is always foo.log
> - On each rollover foo.log is renamed: foo{currentIndex+1}.log
> 
> When number of rollover > maxIndex just start deleting the earlier rollovers
> foo1.log, foo2.log etc...
> 
> 
> 
> 
> --
> View this message in context: http://logback.10977.n7.nabble.com/Change-FixedWindowRollingPolicy-rolling-behaviour-tp14954p14986.html
> Sent from the Users mailing list archive at Nabble.com.
> _______________________________________________
> logback-user mailing list
> logback-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/logback-user