Open aquette opened 7 years ago
I think it would be better to handle the general case first, by implementing a fall-through
Later, specific new
Roger
thanks for all your comments @Luo2Jie2 . ALARM support is to me a good step, which was really missing, and which covers the base status. However, I agree that this filters out "OTHER" (better wording than "UNKNOWN", no?) status changes. We may consider that for a 2nd step.
Calling to @clepple , @zykh , @jimklimov for comments...
"OTHER" is certainly a better name than "UNKNOWN" for a catch-all. Roger
I don't want to sound like I am nit-picking on the name, but if we were to implement a catch-all, wouldn't it be better to make it match everything rather than things not explicitly named? Then it should be possible to have the user-provided notification script do the filtering, without worrying if the notification name has changed at some point.
Also, as of revision f7de20aee, there is an unused variable warning in Buildbot.
postponing to 2.7.6 to have time for the right considerations on this point...
As per http://lists.alioth.debian.org/pipermail/nut-upsuser/2017-April/010591.html
Add support for the ALARM flag in ups.status to upsmon
Development tracked in https://github.com/networkupstools/nut/tree/upsmon_alarm