On Thu, 06.11.14 16:59, Colin Guthrie (gm...@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
On Thu, 06.11.14 14:44, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Thu, Nov 06, 2014 at 02:28:12PM +0100, Lennart Poettering wrote:
On Thu, 06.11.14 12:45, Patrick Häcker (pa...@web.de) wrote:
However, this one appears bogus to me. Is there any such software
around
On Mon, Nov 10, 2014 at 10:53:46PM +0100, Lennart Poettering wrote:
On Thu, 06.11.14 14:44, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Thu, Nov 06, 2014 at 02:28:12PM +0100, Lennart Poettering wrote:
On Thu, 06.11.14 12:45, Patrick Häcker (pa...@web.de) wrote:
On Thursday, 6. November 2014, 14:28:12 Lennart Poettering wrote:
Is unattended-upgrades a package of its own?
Yes, it's a separate package (although it's obviously closely coupled with
the apt package manager).
If so, I'd probably ask the packagers to include drop-ins for
reboot.target to
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
Zbigniew Jędrzejewski-Szmek wrote on 06/11/14 05:52:
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
On Thu, 06.11.14 06:52, Zbigniew Jędrzejewski-Szmek (zbys...@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
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?
At
On Thu, Nov 06, 2014 at 12:48:23PM +0100, Lennart Poettering wrote:
On Thu, 06.11.14 06:52, Zbigniew Jędrzejewski-Szmek (zbys...@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
On Thu, 06.11.14 12:45, Patrick Häcker (pa...@web.de) wrote:
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
On Thu, Nov 06, 2014 at 02:28:12PM +0100, Lennart Poettering wrote:
On Thu, 06.11.14 12:45, Patrick Häcker (pa...@web.de) wrote:
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.
On 11/06/2014 01:28 PM, Lennart Poettering wrote:
However, doing unattended upgrades at shutdown is not really a
common case.
Well for Debian and Debian based distribution it most certainly can be
the case since it has allowed for it's update/upgrade mechanism to be
configured to install
On Thu, Nov 06, 2014 at 02:12:52PM +, Jóhann B. Guðmundsson wrote:
On 11/06/2014 01:28 PM, Lennart Poettering wrote:
However, doing unattended upgrades at shutdown is not really a
common case.
Well for Debian and Debian based distribution it most certainly can
be the case since it
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
On Thu, Nov 06, 2014 at 03:21:33PM +, Simon McVittie wrote:
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
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
On Wed, 05.11.14 17:46, Zbigniew Jędrzejewski-Szmek
(zbys...@kemper.freedesktop.org) wrote:
Ahum.
This needs more discussion.
units: disable job timeouts
For boot, we might kill fsck in the middle, with likely catastrophic
consequences.
This I can agree with for now.
On Thu, Nov 06, 2014 at 03:22:09AM +0100, Lennart Poettering wrote:
On Wed, 05.11.14 17:46, Zbigniew Jędrzejewski-Szmek
(zbys...@kemper.freedesktop.org) wrote:
Ahum.
This needs more discussion.
units: disable job timeouts
For boot, we might kill fsck in the middle,
18 matches
Mail list logo
