[systemd-devel] [systemd-commits] units/basic.target units/poweroff.target units/reboot.target

Lennart Poettering lennart at poettering.net
Mon Nov 10 11:25:37 PST 2014


On Thu, 06.11.14 16:59, Colin Guthrie (gmane at colin.guthr.ie) wrote:

> Simon McVittie wrote on 06/11/14 15:21:
> > On 06/11/14 14:16, Zbigniew Jędrzejewski-Szmek wrote:
> >> > What matters is how it is all arranged:
> >> > 
> >> > - if there's a job that does stuff, and then calls reboot or shutdown
> >> > - a hook into the shutdown or reboot target does some work
> > unattended-upgrades is currently the latter: the user shuts down (or is
> > reminded to shut down by an update notification), and
> > unattended-upgrades runs as a side-effect.
> > 
> > This is an optional (non-default) configuration of an optional package,
> > not core Debian/Ubuntu functionality; so it doesn't necessarily have to
> > be like this forever, it could be modified to tell systemd "I'm still
> > shutting down, continue to wait" periodically, it could be modified to
> > use "reboot into a special mode, install, then reboot again" logic under
> > systemd if that's something you already have, and, worst-case, it could
> > install a drop-in to override the timeout.
> 
> Was there not talk of teaching the sd-notify protocol the ability to
> tell systemd that "I'm still alive and doing stuff - so please don't
> kill me"?

That exists since quite some time. It's the WATCHDOG= field in sd_notify()

Not sure if this is really useful here though...

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list