[systemd-devel] [PATCH 3/4] WIP: manager: add a global watchdog reboot timestamp
Michael Olbrich
m.olbrich at pengutronix.de
Thu Nov 3 03:49:37 PDT 2011
On Wed, Nov 02, 2011 at 02:45:11AM +0100, Lennart Poettering wrote:
> On Mon, 24.10.11 18:04, Michael Olbrich (m.olbrich at pengutronix.de) wrote:
>
> > This patch adds WatchdogRebootTimestamp[Monotonic] to the systemd
> > manager API. It contains the earliest point in time when systemd might
> > reboot the system because the timer for WatchdogRebootUSec for a
> > service expired.
> > If we assume the system takes Xus to shut down then
> > WatchdogRebootTimestamp + Xus should never be in the past. A watchdog
> > daemon handling the hardware watchdog can use this information to
> > determine when to let the hardware watchdog restart the system.
> > This is convenience information for a watchdog daemon. With this the
> > it can avoid a lot of D-Bus calls that are necessary to calculate the
> > same value.
>
> Hmm, wouldn't it be nicer to generate this value on the fly on the
> server side when a client asks for it? i.e. instead of having an actual
> field watchdog_timestamp just fake it when the client asks for it?
Of course, I just need to figure out how to do this :-). Can you point me
to some other property that does something like that?
> WHat I am not getting here, don't you also want to send out
> notifications each time the watchdog timestamps are refreshed?
Same reason. I don't know how to do that yet. Again an pointer to an
existing property doing that would be great.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the systemd-devel
mailing list