[ 
https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021989#comment-15021989
 ] 

Robert Schaft commented on LOG4J2-435:
--------------------------------------

Remko,

I understand your problem with the database. There might be synchronization 
problems and it could get lost. Also the disk full case could be troublesome.

Nevertheless it seem to me, that you are creating the configuration 
requirements from the implementors perspective. Please try to change your 
perspective to the users standpoint:
- Does the naming of elements, attributes and arguments really tell what is 
going on? (What is mostRecent="true"? Or what is duration? Isn't that the age? 
Does "Delete" only delete rolledOver files?)
- Is the naming consistent? ("If..." within "And", "If..." next to non-"If...")
- Most important: Can't we find a way to avoid pulling this information from 
the user? Can't the values be calculated based on other values? Are there good 
defaults?




> Feature request: auto-delete older log files 
> ---------------------------------------------
>
>                 Key: LOG4J2-435
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-435
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Arkin Yetis
>            Assignee: Remko Popma
>              Labels: Rollover
>             Fix For: 2.5
>
>         Attachments: LimitingRolloverStrategy.java, SizeParser.java
>
>
> Original description:
> {quote}
> DefaultRolloverStrategy max attribute only applies if you have a %i in the 
> file pattern. This request is to enhance DefaultRolloverStrategy or another 
> appropriate component to allow a max number of files limit to apply across 
> days/months/years when a filePattern includes a date pattern.
> {quote}
> ----
> One of the most requested features is to add the ability to Log4j to "clean 
> up" older log files.  This usually means deleting these files, although it 
> could also mean moving them to a different location, or some combination of 
> these. 
> Users have different requirements for selecting the files to clean up. A 
> common request is the ability to keep the last X number of log files. This 
> works well if rollover is only date based but may give undesired results with 
> size based rollover. 
> Another factor to consider is that the directory containing the log files may 
> contain the log files for multiple appenders, or even files unrelated to 
> logging. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to