Hi, this is just a rebase to the current master. I sent these patches before, but I didn't get any comment for this version. The first 3 patches are imho ready to be merged.
The last patch is just RFC for not. Lennart asked if this could be done inside systemd itself. So I tried to implement the /dev/watchdog handling inside systemd itself, but I'm not sure where to put it. I think it could be done as a unit. However, that would be a new type and there will only ever be one, so I'm not so sure this is the right way to do it. A unit would be nice to provide all the infrastructure: enable/disable, configuration, unit timer, etc. If not, the configuration could come from the global config file, cmdline and kernel cmdline, but the rest? So, to those of you that have a better understanding of the internal design of systemd: what's the best way to do this? Regards, Michael Michael Olbrich (4): service: add watchdog timestamp service: add watchdog restart/reboot timeouts manager: add a global watchdog reboot timestamp WIP: add basic watchdog daemon Makefile.am | 22 ++++- man/sd_notify.xml | 12 +++ man/systemd.service.xml | 32 +++++++ src/99-systemd.rules.in | 2 + src/dbus-manager.c | 39 ++++++++ src/dbus-service.c | 9 ++ src/load-fragment-gperf.gperf.m4 | 2 + src/sd-daemon.h | 5 + src/service.c | 48 ++++++++++ src/service.h | 6 + src/watchdogd.c | 178 ++++++++++++++++++++++++++++++++++++ units/systemd-watchdogd.service.in | 16 +++ 12 files changed, 369 insertions(+), 2 deletions(-) create mode 100644 src/watchdogd.c create mode 100644 units/systemd-watchdogd.service.in -- 1.7.7.3 _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
