[systemd-devel] Question about hardware watchdog

Lennart Poettering lennart at poettering.net
Mon Nov 5 18:29:05 UTC 2018


On Mo, 05.11.18 16:21, Liu, Shuang (ADITG/ESM) (sliu at de.adit-jv.com) wrote:

> Hi,
> 
> We are facing problem with hardware watchdog.
> 
> To my understanding, the watchdog is pinged inside the manager_loop(),
> which means, during e.g. systemctl daemon-reload, watchdog cannot be pinged.
> 
> Here, perhaps other timeouts are involved in, e.g. generator timeout, dbus timeout, systemctl timeout, ...
> which could be larger than the RuntimeWatchdogSec.
> 
> Thus a problem with systemctl daemon-reload could trigger the watchdog timeout.

Yes, and that's intended. If an event is dispatched (such as a reload
request) and we don't return to normal event loop processing within
the watchdog timeout, then the watchdog will react and reboot. 

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list