On Thu, 02.02.12 19:42, Lennart Poettering ([email protected]) wrote: > a) track the watchdog alive messages (already merged) > > b) hook up the watchdog with the existing failure logic and introduce > WatchdogSec for that. > > c) pass watchdog frequency to executed processes via env var > > d) replace failure boolean with an enum > > e) extend start logic to do configurable rate limiting of starts, > plus optionally reboots when rate limiter is triggered. New options for > this: > > StartLimitInterval=5min > StartLimitBurst=5000 > StartLimitAction=none|reboot|reboot-force|reboot-immediate > > f) hookup /dev/watchdog with all of this > > Of these b) and c) should be fairly easy. I will implement d) in the > next half hour. e) is fairly easy since we already have ratelimit.c > which can be trivially reused i guess, and we actually already have a > static ratelimiter for this built-in, so this is mostly about adding > configurability and the reboot options to it. f) I am not entirely sure > how this should look in the end, need to think about this more.
I ave now implemented d), it's available in git. There's now a ServiceResult enum in service.h which should be extended for SERVICE_FAILURE_WATCHDOG. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
