DO NOT REPLY [Bug 11474] New: - Improvements to rolling file appenders

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11474>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11474

Improvements to rolling file appenders

           Summary: Improvements to rolling file appenders
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: ats37@hotmail.com


I have the following enhancement requests for the RollingFileAppender and 
DailyRollingFileAppender:

1) allow RollingFileAppender to keep unlimited backups.
2) to save time and effort renaming every backup file each time they roll, add 
an option to have the RollingFileAppender use the date & time of rolling for 
the renamed file instead of a number e.g. mylog.20020805171622 (for 4:16:22 pm 
5th Aug '02) instead of mylog.1 (or, perhaps, .2002-08-05-17-16-22 to more 
closely resemble the DailyRollingFileAppender's naming).
3) to save storage space used by old log files, add an option to the 
RollingFileAppender to automatically compress (ideally as a zip file, or 
perhaps a choice of methods) the rolled files after renaming.
4) as an alternative to keeping a certain (fixed) number of old backup files, 
add an option to the RollingFileAppender for a maximum age of file to be kept 
instead (so I can e.g. have it automatically delete any log files more than a 
week old).  The timekeeping needn't be strict, just check each time a file is 
rolled.  Obviously, it should only be done for files whose initial filename 
matches, since multiple appenders might be writing their files to the same 
directory.
5) as well as an option for the maximum number of files to keep, add an option 
for the minimum number.  This is useful in conjunction with the maximum age 
option to e.g. delete everything over a day old, but keeping at least the last 
three backups even if they're older.
6) it seems to me that the DailyRollingFileAppender does a similar job to the 
RollingFileAppender; the difference is the triggering condition, current time 
vs. size of log file.  In my opinion, the two could be usefully combined to 
give an appender which rolls over based on either date/time or size depending 
on the options specified.  This would allow DailyRollingFileAppender to take 
advantage of the maxBackupIndex backup renaming, in addition to the features 
described above.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>