[systemd-devel] drop-ins and watchdogs question

Mantas Mikul─Śnas grawity at gmail.com
Sat Mar 21 13:51:55 PDT 2015


On Sat, Mar 21, 2015 at 10:07 PM, Alison Chaiken <alison at she-devel.com>
wrote:
> To stop systemd from petting the dog, I create a new system.conf file
that has
>
>                  RuntimeWatchdogSec=0
>
> and type 'systemctl daemon-reexec'.   As expected, 'sudo lsof
> /dev/watchdog' shows no one is holding file open.   However, the
> system does not reboot!

I *think* systemd closes the watchdog device cleanly when you disable it
via config, so the hardware timeout is no longer 'active'. Would be quite
surprising to the user, if it didn't.

Try suspending systemd (SIGSTOP) or crashing it (SIGSEGV).

-- 
Mantas Mikul─Śnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150321/28c8cd4f/attachment.html>


More information about the systemd-devel mailing list