I have to have per-client logfiles for my environment. We have about 100 concurrent users so I am going to have RollingFileAppenders for each logger. My problem is going to be disk space. Some of the clients will do a lot of logging, others will be very sparse. My fear is that I won't be able to use the maxFiles and fileSize values to make sure the logs don't use too much space. Assuming all clients will log heavily and capping the maxFiles and fileSize accordingly will be prohibitively sub-optimal. Any other usage of those 2 values to limit log proliferation is inherently dangerous.
I was wondering whether anyone else has had this problem and how they fixed it. My current plan is to subclass RollingFileAppender and have it delete the last touched file when the total log-space-used gets above a certain size. After a while, this will entail the overhead of finding which is the oldest log-file (in order to delete it) every time a new file is created. Does anyone have a better idea? alan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
