"snap set system watchdog.*" settings aren't applied immediately
Bug #1854694 reported by
Robert Liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
High
|
Samuele Pedroni |
Bug Description
When setting/updating the hardware watchdog timer through "snap set system watchdog.
"watchdog.
tags: | added: original-1853401 |
Changed in snapd: | |
importance: | High → Medium |
summary: |
- Watchdog settings don't be applied immediately + Watchdog settings aren't applied immediately |
Changed in snapd: | |
assignee: | nobody → Samuele Pedroni (pedronis) |
Changed in snapd: | |
importance: | Medium → High |
Changed in snapd: | |
status: | Triaged → In Progress |
Changed in snapd: | |
status: | In Progress → Fix Committed |
Changed in snapd: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Robert, I'm not entirely familiar with semantics of watchdog in systemd, but after a quick scan of the code I can confirm that: watchdog. conf from core watchdog. runtime- timeout and shutdown-timeout (on any change to the value), however we don't trigger any restart/reload (just write the file for systemd).
- we regenerate 10-snapd-
- on snapd startup we read WATCHDOG_USEC interval and keep notyfing systemd according to it, but since we don't restart, we will not pick up any new value that systemd may give us.
Does this make sense and correctly reflects the problem?