I was messing with something, and I noticed that threshold events with
the direction bit set to deassertion do not get printed as a deassertion
in ipmitool. Since that is quite clearly supported in the spec, and you
would expect this is what would happen when an event goes back in range,
why is that?
It's pretty simple to fix, the following patch changes it it. But that
patch also makes it pretty clear that this was on purpose. What's the
Get latest updates about Open Source Projects, Conferences and News.