apt/debian/apt.systemd.daily, branch 1.3_pre1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_pre12016-06-27T09:22:02ZUse the ConditionACPower feature of systemd in the apt-daily service2016-06-27T09:22:02ZNicolas Le Camniko.lecam@gmail.com2016-06-22T19:39:38Zurn:sha1:51d659e7d8cdce59f910eceeee68e2c2afdb70d4
.. instead of hardcoding the functionnality in the apt.systemd.daily
script.
Also make the compatibility cron job provide the same functionnality
for systems that do not use systemd.
Closes: #827930
apt.systemd.daily: Put opening brace of check_power on extra line2016-05-15T16:13:14ZJulian Andres Klodejak@debian.org2016-05-15T16:11:48Zurn:sha1:ea4c6b3ec839976c205c05984c2a64b77bac5317
The rest is also on the same line, so let's go consistent here
now that we have a bug report about it.
LP: #1581985
Use systemd.timer instead of a cron job2016-04-01T11:02:39ZMichael Vogtmvo@ubuntu.com2016-03-17T07:56:58Zurn:sha1:14669d4b95f0f6a9b215d7fa5aebbc3b7198585d
The rational is that we need to spread the load on the mirrors
that apt update and unattended-upgrades cause. To do so, we
leverage the RandomizeDelay feature of systemd. The other advantage
is that the timer is not run at a fixed daily.daily time but
instead every 24h. This also fixes the problem that the randomized
deplay in the current apt.cron.daily causes other cron jobs to
be deplayed.
A compatibility cron job is also provided for systems that do not
use systemd.
Note that the time is fired two times a day, but the logic inside
of apt.systemd.daily will ensure (via stamp files) that the
servers are hit at most every 24h. Firing two times a day helps
with the worst case update time and it also helps with systems
that are not always on.
LP: #246381, #727685
Closes: #600262, #709675, #663290