Exported from Bugzilla, issue 2092.
--- Comment added on 12/11/2001 2:09:01 PM ---
Scott Carter, 12/11/2001
Logs can become too large -- taking up too much space and becoming so large
that it's hard to find an app to open them. In many situtations, only the last
x lines are of value also.
It would be nice to be able to purge the physical log once it gets to a certain
size. IOW, once the the file gets to be 100 megs delete all but the last 1000
lines (or some size: like keep the last 1 meg).
--- Comment added on 12/13/2001 2:49:44 PM ---
I think we talked about something like this during the design phase?
--- Comment added on 9/12/2002 2:45:29 PM ---
In the present architecture, the Logging components have no facility for
re-interpreting an existing physical log to make sense out of previously dumped
entries. Adding that seems like it would overly complicate the components.
Given that the physical log is a plain text file, the user has the option of
easily clobbering all but the last N lines if they want, or simply deleting the
existing file before dumping.
We could easily add facilities to the components to support doing both of those
options, but is it worth it?
--- Comment added on 9/12/2002 3:10:37 PM ---
A better approach at some point in the future might be to add some sort
of "rotation" capability to the log. In other words; rename existing logs on a
periodic basis (daily, weekly, whatever) and write to a new file (this type of
scheme is popular in *NIX).
I agree that it isn't worth putting time into this type of thing at the moment.