apt/debian/apt-daily.timer, branch 1.3_exp2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_exp22016-04-04T14:52:27ZFix `OnCalendar=*-*-* 6,18:00` instead of `OnCalendar=*-*-* 6:00,18:00`2016-04-04T14:52:27ZMichael Vogtmvo@debian.org2016-04-04T14:52:27Zurn:sha1:c9a2e4db0001729574bfe52d6663d066f0c59baa
See https://github.com/systemd/systemd/issues/2956 - it appears that
`OnCalendar=*-*-* 6,18:00` and `OnCalendar=*-*-* 6:00,18:00` are
quite different.
Git-Dch: ignore
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