Browse Prior Art Database

Method to control pruning of a history log based on user-settable parameters

IP.com Disclosure Number: IPCOM000126406D
Original Publication Date: 2005-Jul-15
Included in the Prior Art Database: 2005-Jul-15
Document File: 1 page(s) / 25K

Publishing Venue

IBM

Abstract

Disclosed is a method by which growth of a history log is kept in check by periodic pruning of the entries. The user is given the ability to control the pruning to save only as much history as they would like. As an example of a history log, in a printer, jobs are received and then printed. It is useful to maintain a log that details all the jobs that have gone through the system and information about those jobs. However, the number of such jobs grows continually, and can get quite large, meaning your job history log also becomes large, possibly large enough to adversely affect the rest of your printer (not enough space).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 85% of the total text.

Page 1 of 1

Method to control pruning of a history log based on user -settable parameters

The following is the description of how the history log is pruned periodically using configurable settings. This solution is flexible, such that it can be used effectively by users whose workload creates lots and lots of entries, by users that create entries infrequently, and by users that do a bit of both.

     Pruning will be performed using three configurable settings: - "Maximum number of entries" - "Maximum time since completion" - "Use max entries and/or max completion"

     The "Use max entries and/or max completion" item would have one of five possible values:

entries Limit log based only on "Maximum number of entries"item. time Limit log based only on "Maximum time since completion" item. neither Use neither of the items, such that there is no limit to the log (that is, user intervention is required to prune the log). either Limit log based on both of the items such that the log is pruned if it is too big based on either of the items. both Limit log based on both of the items such that the log is pruned only if it is too big based on both maximums.

These three parameters define a "pruning policy".

     The way to change the pruning policy, then, is to change these three configuration values. The history pruning component will pick up the changes the next time pruning is performed.

     However, it is also possible to call a function to prune the history log immediately. This function would take th...