DO NOT REPLY [Bug 13947] - DailyRollingFileAppender.rollover() uses default access

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

DailyRollingFileAppender.rollover() uses default access





------- Additional Comments From joerattz@yahoo.com  2003-08-14 14:52 -------
I would like to see the functionality of DailyRollingFileAppender changed to 
accomplish what this entry is requesting.  What is the purpose of having a 
rolling logger if it will always generate a unique logname?  What I mean is 
that in all documentation/examples I can find, the log file names always end up 
being unique via some component of the date that includes year.  This will 
result in an infinite number of files and this creates a maintenance problem, 
someone will have to periodically delete files.  For example, a daily rollover 
results in something like mylog.log.2003-8-01 (format may not be correct, just 
example).  This means that no files will ever write over existing older files.  
If instead, the daily rollover had a file name more like mylog.log.monday (for 
first day of week configuration), or mylog.log.07 for the 7th of the month (for 
a day of the month type configuration), then at least at some point (weekly or 
monthly), the logs would overwrite the old ones thereby making external file 
deletion unnecessary.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org