The TimeAndSizeRollingAppenderat www.simonsite.org.uk might do the trick by configuration. You can configure a time-based rolling schedule via a date pattern. There's also a scavenger built-in that will delete older backup log files beyond a particular count. So if you configure the appender to roll daily, and set the max backup count to the number of days you're interested in, the scavenger will delete the files you no longer want. The scavenger runs in a daemon thread so you don't have backup log files being maintained at the point of rollover of the current log file.
HTH, Simon ________________________________ From: Jacob Kjome <[email protected]> To: Log4J Users List <[email protected]> Sent: Thu, 14 October, 2010 16:38:31 Subject: Re: RollingFileAppender + TimeBasedRollingPolicy Not that I can see. I think a FixedWindowRollingPolicy + SizeBasedTriggeringPolicy would do what you need. Of course, it won't roll based on time, but on size. Basically, you'd get a maximum backup of 12 (or less depending on what you configure) archived log files, which is hardly different than deleting old files. That said, you might be able to [ab]use a FilterBasedTriggeringPolicy to trigger rolling based on time (and/or size). Note that I have not tested this myself. It would be interesting to learn of your results. Jake On 10/14/2010 4:50 AM, Corey Scott wrote: > Hi there, > > Is there some param i can set in the log4j.xml to have the > TimeBasedRollingPolicy delete old files after x days? > Im sorry if this is handled in the doco and Im too stupid to find it :) > > Cheers, > Corey > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
