dbus-sensors

[Brad Bishop]

at 8:11 AM, Patrick Williams <patrick at stwcx.xyz> wrote:

> On Wed, Apr 22, 2020 at 07:56:14AM -0400, Brad Bishop wrote:
>> at 5:54 PM, James Feist <james.feist at linux.intel.com> wrote:
>>>> 3. After creating this event log, make sure not to do it again until
>>>>    main power is cycled.
>>>
>>> I'd rather this be until the status goes OK again.
>>
>> We have user-experience requirements that the server administrator must be
>> “nagged” in this fashion when something is broken like this.  Could the
>> behavior be selectable via build switch?  Any other ideas on how to
>> accommodate both behaviors?
>
> This sounds like a form of error filtering.  Shouldn't that decision be
> done at a much higher level in the stack than down in the entity that
> reads the hardware sensor?

Thats an interesting thought.  When the error reporting code sees the error  
for the first time, it could maintain a list of errors that it needs to  
“replay” at different system events, like when the server powers on.

This is certainly more flexible and I like the idea - but one down side  
though is the logging code becomes stateful and the complexity is slightly  
higher.