Remko, that is not exactly correct. If you specify %i in the filePattern once the max value is hit the oldest file that matches the complete pattern will be deleted automatically. The issue you are speaking of is that when the pattern includes a date via %d we will not delete files from previous dates.
If the pattern only contains %d and does not contain %i then the files will never be deleted by Log4j. Ralph On Jul 30, 2014, at 3:44 PM, Remko Popma <remko.po...@gmail.com> wrote: > The built-in rollover only moves/renames but never deletes files. (We > actually have outstanding enhancement request to add some auto-delete > function.) > > Sent from my iPhone > >> On 2014/07/31, at 4:30, Mariano Gonzalez <mariano.l.gonza...@gmail.com> >> wrote: >> >> Hello, >> >> I'm configuring a RollingFileAppender programatically, using a >> TimeBasedTriggeringPolicy in tandem with a DefaultRooloverStrategy. So far >> so good, but is there a way to provide a RolloeverStrategy which renames >> the files but never deletes them? >> >> Thanks! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
