-
Key: TLOG-57
-
Legacy Issue Number: 9261
-
Status: open
-
Source: Identity Engines, Inc. ( J.T. Conklin)
-
Summary:
I am the current maintainer of the TAO logging service implementation. The specification is unclear what the interactions between set_max_size(), set_log_full_action(), and set_capacity_alarm_thresholds() have on the current processing of capacity alarms. For example, consider a log with DsLogAdmin::halt log full action and 0 (ie. infinate) max size, and a capacity alarm threshold list of [50, 75, 90, 100]. If the log has 80KB of records, and the max size is set to 100KB, are ThresholdAlarms supposed to be sent for crossing 50 and 75%, or should a threshold alarm only be sent once the log grows to 90%? Similar questions arise when the log full action is changed to/from DsLogAdmin::halt from/to DsLogAdmin::wrap, as the capacity alarm threshold processing changes from a percentage to a "gauge". Or when the capacity alarm threshold list is changed from one set of values to another.
-
Reported: TLOG 1.1.2 — Tue, 24 Jan 2006 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:58 GMT