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

[Zbigniew Jędrzejewski-Szmek]

On Fri, Nov 07, 2014 at 03:02:49PM +0100, Patrick Häcker wrote:
> That should be possible. Currently the package contains 
> /lib/systemd/system/unattended-upgrades.service which contains:
> > [Unit]
> > Description=Unattended Upgrades
> > DefaultDependencies=no
> > Before=shutdown.target reboot.target halt.target
> > Documentation=man:unattended-upgrade(8)
> > 
> > [Service]
> > Type=oneshot
> > ExecStart=/usr/share/unattended-upgrades/unattended-upgrade-shutdown
> > 
> > [Install]
> > WantedBy=shutdown.target
> 
> Only the maintainer Michael Vogt can decide if he wants to go in that 
> direction, thus I added him as CC.
> 
> @Michael Vogt:
> The discussion is about adding a watchdog to systemd to power down the system 
> if the shutdown takes longer than some time (i.e. 30 minutes). The question 
> was how to avoid killing unattended-upgrade during a longer upgrade if it is 
> configured to update the packages at shutdown.

Systemd has to provide a mechanism, but how it is to be implemented is our
problem. I don't think that this is a question for maintainers of other packages
to answer.

> On Thursday, 6. November 2014, 14:28:12 Lennart Poettering wrote:
> > If so, I'd probably ask the packagers to include drop-ins for
> > reboot.target to override the timeout. That way, as soon as you install
> > it the shutdown timeouts are disabled.
That's not nice. Installed but unused should not matter.

I think we should be asking a different question: does the upgrade process
currently run a a job after shutdown.target or reboot.target is scheduled?

Zbyszek