[jboss-jira] [JBoss JIRA] (LOGMGR-139) Add maxBackupIndex to periodic-rotating-file-handlers

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/LOGMGR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253680#comment-13253680 ] 

James Perkins commented on LOGMGR-139:
--------------------------------------

This is a rather complicated problem to solve. Since the suffix can be set to nearly any supported by {{java.text.SimpleDateFormat}} it makes it very difficult to parse file names to determine which files would be available for purging. There are some things that could be done to make some assumptions about file names, but having a log manager make assumptions about files on a file system seems wrong. You wouldn't want your log manage to delete files it shouldn't be deleting because it made an assumption about a file name.

One option besides a custom handler is to use tools on the OS, like a cron job on Linux, to purge older files.

As far as not getting your custom handler to work I'm guessing you mean on WildFly or JBoss EAP. What seems to be the issue there?

> Add maxBackupIndex to periodic-rotating-file-handlers
> -----------------------------------------------------
>
>                 Key: LOGMGR-139
>                 URL: https://issues.jboss.org/browse/LOGMGR-139
>             Project: JBoss Log Manager
>          Issue Type: Enhancement
>            Reporter: Rémy Garrigue
>            Priority: Minor
>
> That's all in the title. 
> We would like to have a daily log, keeping 15 days of log. Actually there's no way to do that except maybe custom handler which we can't get to work. That'ld be far easier if there was the same maxBackupIndex  option as in size rotating handler.
> Regards, 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)