DO NOT REPLY [Bug 11907] New: - DailyRollingFileAppender should extend RollingFileAppender

[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=11907>.
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=11907

DailyRollingFileAppender should extend RollingFileAppender

           Summary: DailyRollingFileAppender should extend
                    RollingFileAppender
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: piper@vcgsoftware.com


There is currently no safe way to limit the amount of disk space consumed by a 
DailyRollingFileAppender. The DailyRollingFileAppender should be configurable 
with MaxFileSize and MaxBackupIndex properties like RollingFileAppender. 
Further still, the DailyRollingFileAppender should extend RollingFileAppender.

1. MaxBackupIndex would limit the number of log files.
2. MaxFileSize would limit the size of any specific log file.

When MaxFileSize is exceeded, you could segment the log files for the current 
period. Each segment would be limited to MaxFileSize, but there could be one 
or more segments for each period. For example:

    mylog.txt   (current log file - second segment for this period)
    mylog.1.txt (first segment of log file for this period)
    mylog.2002-08-20.1.txt (first segment of file for last period)
    mylog.2002-08-20.2.txt (second segment of file for last period)
    mylog.2002-08-21.txt (only segment for two periods ago)

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