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

http://issues.apache.org/bugzilla/show_bug.cgi?id=28961

loggers shift files but don't roll (not deleting oldest files by prescribes file count)

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |
            Summary|provide new Log4J/java2-    |loggers shift files but
                   |logging-api proxy loggers   |don't roll (not deleting
                   |class                       |oldest files by prescribes
                   |                            |file count)



------- Additional Comments From [EMAIL PROTECTED]  2004-05-27 14:48 -------
System integrators consider this RFE seriously.

Please take your time to fully understand the consequence and do not discard the
idea because the singular piece of code you seam to focus on will not be
updated. You are free to carry this RFE to the most up to date logging framework
catalina intent to use, but in the mean time, tomcat 5.0.24 user do not have
access to those updates.

You effectively said to every tomcat users, that they must start writing
scripts, or task, or cron jobs, or logrotate setup, or background thread in a
monitoring servlet, that will monitor a file system for logs and delete older
ones manually. This is a waste of energy, as the logger itself can do a simple
check, as it is already aware of every log details.

"Rolling" implies the concept of circular buffer and means that the size of the
storage is finite.

You can't affrim your logs rotate unless you guaranty the log storage won't
exceed a prescribes size, time or filecount.

You logger barely "shifts" files, which is just a convenient implementation
choice, but doesn't fulfill the "rolling" requirements.

The lack of this feature makes it difficult for system integrators to deploy
apps without having to worry about badly behaving loggers that effectively leaks
on hard disk.

Thanks for reconsidering this request.

Note: I don't get that Remy thing you are refering to, but remember that
everyone hears a voice when they read, and that voice is reflecting the mood and
attitude of the reader. I don't know how my texts were interpreted, but I mostly
 push non-objectively when thing really don't make sense. That should ring a
bell to you guys, that there is something serious going on, and not just a
stupid guys personnal favor. I don't have time to waste on simple things. So if
you feel I'm harsh, I feel you are not very understanding at the same time, so
why don't we read each other in a perfectly objective way, sifting only the core
message. 

Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to