logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: RFE - Fixed Memory Logging
Date Tue, 04 May 2004 17:00:41 GMT

Hi,
OK.  That's not even close to what I understood from the original
message, so disregard all my comments ;)

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Alan Brown [mailto:abrown@opstechnology.com]
>Sent: Tuesday, May 04, 2004 12:57 PM
>To: Log4J Developers List
>Subject: RE: RFE - Fixed Memory Logging
>
>
>My plan is actually to allow a relatively large amount of logging, but
>to be certain it wasn't going to get too large.  By 'unmanageably
large'
>I mean the cost of opening the file over the network.  I also have an
>odd configuration as I'm doing per-client logging, so I'm forced into
>using multiple appenders.  So I envisioned a central Log File Manager
>that would know which files to delete when the overall logging disk
>space got beyond an acceptable amount.  My system is very logging
>intensive (approaching a gig and a half a day), and as we move from a
>single RollingFileAppender model to a per-client logging model we gain
>the issue of how to do intelligent rollovers and deletions of many
>different files.
>
>alan
>
>-----Original Message-----
>From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
>Sent: Tuesday, May 04, 2004 9:37 AM
>To: Log4J Developers List
>Subject: RE: RFE - Fixed Memory Logging
>
>
>Hi,
>
>>Unfortunately that wouldn't work for me, because it would mean I'd
have
>>one unmanageably large log file and then I'd lose all my logging when
>>the file filled up.
>
>Unmanageably large?  How so when you can precisely define the maximum
>size of the file?
>
>I also thought the point was to limit the storage used by log files
even
>at the expense of losing additional logging.  I guess I misunderstood
>your requirements.
>
>Yoav Shapira
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary and/or privileged.  This e-mail is intended only for the
>individual(s) to whom it is addressed, and may not be saved, copied,
>printed, disclosed or used by anyone else.  If you are not the(an)
>intended recipient, please immediately delete this e-mail from your
>computer system and notify the sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-dev-help@logging.apache.org




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


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


Mime
View raw message