I looked into this and it seems that if a count is used to determine the
file to be deleted, some of the information needed (interval, modulate) is
in the TimeBasedTriggeringPolicy and the DefaultRolloverStrategy does not
have that information.
Would it be a good idea to introduce the concept of a
OK - feel free to submit a patch!
Ralph
On Oct 19, 2013, at 8:47 PM, Arkin Yetis wrote:
> Thanks, opened https://issues.apache.org/jira/browse/LOG4J2-435.
>
> Arkin
>
>
> On Tue, Oct 15, 2013 at 8:34 AM, Ralph Goers
> wrote:
>
>> Not currently. You should create a Jira to request it. I s
Thanks, opened https://issues.apache.org/jira/browse/LOG4J2-435.
Arkin
On Tue, Oct 15, 2013 at 8:34 AM, Ralph Goers wrote:
> Not currently. You should create a Jira to request it. I suppose the max
> attribute could be used to limit the number of days if no %i is present,
> but if it is then
Not currently. You should create a Jira to request it. I suppose the max
attribute could be used to limit the number of days if no %i is present, but if
it is then it would only apply to that so it really wouldn't limit the total
number of files. So I am thinking a second attribute might be a
Got it. It is rolling. I thought it would limit across days, too. Is there
a way to do cleanup across days currently?
Thank you.
- Arkin
On Tuesday, October 15, 2013, Ralph Goers wrote:
> What behavior are you seeing? Is it never rolling or something else?
>
> The max attribute only applies if
What behavior are you seeing? Is it never rolling or something else?
The max attribute only applies if you have a %i in the file pattern. It would
limit to 2 files per day if you had one in the patten, but not 2 files across
days.
Ralph
> On Oct 14, 2013, at 6:07 PM, Arkin Yetis wrote:
>
>
Hi,
I can't seem to get the DefaultRolloverStrategy to work with the following
configuration. Is there anything I am doing wrong?
Thanks,
Arkin
