I've checked both systemd and snapd. Here are my findings, but I'm not sure if I missed something.
1. systemd will notify the hardware watchdog if we set the "RuntimeWatchdogSec"[1]
2. Systemd parses the .service file of snapd and pass the value through the WATCHDOG_USEC env variable. By default, the value is 5 minutes. Systemd will restart snapd, if snapd doesn't update the software watchdog within the period.
So, I think it's should be fine that using "systemctl daemon-reexec" to apply the watchdog settings immediately after updating.
Hi Pawel,
I've checked both systemd and snapd. Here are my findings, but I'm not sure if I missed something. gSec"[1]
1. systemd will notify the hardware watchdog if we set the "RuntimeWatchdo
2. Systemd parses the .service file of snapd and pass the value through the WATCHDOG_USEC env variable. By default, the value is 5 minutes. Systemd will restart snapd, if snapd doesn't update the software watchdog within the period.
So, I think it's should be fine that using "systemctl daemon-reexec" to apply the watchdog settings immediately after updating.
[1] https:/ /git.launchpad. net/ubuntu/ +source/ systemd/ tree/src/ core/manager. c?h=ubuntu/ xenial- updates# n2019