jcoffland
commented
14 years ago Comment by @bb30994 Note: This is already a bigger problem in v7 than in v6. In v7, you create a fresh log every time the client is restarted. In v6, a restart when FAHlog is less than 50K does not create a new log, but simply appends more information to the log.
I'm not saying that appending to the v7 log is a good idea, but log management and log filtering are a much bigger issue in v7 and often it's really hard to find the information I'm looking for.
I know you have plans to provide log-filtering. One very important feature thay you may or may not have considered: The functional equivalent of FAHlog-Prev.
I need to be able to select a slot and see what has happened to it, whether the client has been restarted or not. That means you need to be able to filter the archived logs as well as the current log. In V6, the amount of data presented is limited, somewhat, by the cutoff process of creating FAHlog-Prev periodically but the option is still available to spend XX seconds filtering the log and then optionally saying "I want even more history" . . . and pre-pending even older information. (I see a potential performance issue if you filter everyting and I'm suggesting one possible fix.)
Some donors create their own backup copies of FAHlog-Prev(-Prev), etc. but that's probably excessive.