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

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

Ralph,
It might be partly my poor English. But I was not aware of your participation 
in log4j2. If I would have checked, it would have simplified the discussion.

I don't know if you did it on purpose. But the limited configuration options 
are also a big plus for log4j2. You know that the code behind was already 
tested with various inputs and that it doesn't crash during runtime.

What happens if a delete script fails after a while? Will the system shut down? 
Will it silently fill your harddisk?
What happens if it runs runs too long? How long does it's namespace live?

Additionally it allows guys from the Operations team to program. I (as 
developer) don't want to support that code.
If you want to open the pandoras box of scripting, you are of course free to do 
so.
But it should't be part of this Feature Request from my point of view.


> 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