On Sat, Mar 21, 2015 at 10:07 PM, Alison Chaiken <[email protected]> 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 <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
