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

[Zbigniew Jędrzejewski-Szmek]

On Thu, Nov 06, 2014 at 12:48:23PM +0100, Lennart Poettering wrote:
> On Thu, 06.11.14 06:52, Zbigniew Jędrzejewski-Szmek (zbyszek at in.waw.pl) wrote:
> 
> > > >     On shutdown there might be other jobs, like downloading of updates for
> > > >     installation, and other custom jobs. It seems better to schedule an
> > > >     individual timeout on each one separately, when it is known what
> > > >     timeout is useful.
> > > 
> > > However, this one appears bogus to me. Is there any such software
> > > around that really does this? And if so, this really appears weird to
> > > me to support. Delaying shutdown for more than 30min is just wrong.
> >
> > Isn't this what the various "download updates and reboot" gnome-y
> > things are doing?
> 
> No, they shutdown, reboot into a special mode, install, reboot again.
I know that package *installation* is done after reboot. I was thinking that
the *download* was done during shutdown. But it appears that the 'install
and shutdown' dialog button appears only after they have been downloaded.
In other words, they are downloaded while system is running. It seems that
indeed there's no reason for long shutdowns right now. I reenabled the
timeouts now in git.

Zbyszek