[PATCH phosphor-event] Create a possible limit to the number of logs recorded

OpenBMC Patches openbmc-patches at stwcx.xyz
Tue May 17 15:40:37 AEST 2016


https://github.com/openbmc/openbmc/issues/268

There was a technique that created over 1000 event logs.  This taxed
the REST interface a lot.  It caused connections to time out.  I am
adding a way to limit the number of physical logs irregardless of the
size.  Like the size limiter, logs are not deleted automatically.

That may actually be a debate (save new logs, delete old logs) vs
(delete new logs, save old logs).  I welcome the suggestions.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/openbmc/phosphor-event/18)
<!-- Reviewable:end -->


https://github.com/openbmc/phosphor-event/pull/18

Chris Austen (1):
  Create a possible limit to the number of logs recorded

 event_messaged.C | 10 +++++++---
 message.C        | 14 ++++++++++++--
 message.H        |  3 ++-
 test.C           | 59 +++++++++++++++++++++++++++++++++++++++++++++++++-------
 4 files changed, 73 insertions(+), 13 deletions(-)

-- 
2.8.2




More information about the openbmc mailing list