admin/Linux_post_install
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: report skipped rules in event-trigger run; add lm-sensors dep

Browse Source 
- run now counts rules skipped because their check produced no number (or
  the line was unparseable) and reports both counts, so an all-skipped pass
  no longer reads as 'evaluated 0 rule(s)'.
- preinstall.sh installs lm-sensors — the sensor example rules in event.env
  need it; howto troubleshooting notes to check 'sensors -u' output for the
  real *_input key before adding a rule.
This commit is contained in:
Your Name
2026-08-09 17:31:59 +00:00
parent 030ec0b456
commit 577d49ac2d
4 changed files with 16 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DOC/howto/event-trigger.md
+5 -1
View File
@@ -46,7 +46,11 @@ Examples:
Behavior:
- The check runs on every pass. Non-numeric/empty output, or an unparseable
line → the rule is skipped with a warning (other rules still run).
line → the rule is skipped with a warning (other rules still run). The
`run` summary reports how many rules evaluated and how many were skipped.
- `sensors` rules need `lm-sensors` installed (`preinstall.sh` installs it;
verify with `sensors -u` before adding a rule — sensor names differ by
chip, check `sensors -u` output for the real `*_input` key).
- Alerts fire **once** when the condition turns true, and once more when it
recovers — a hot CPU for two hours is one message, not twenty.
- State is tracked per rule in `~/.local/share/linux_post_install/eventer/state/`