<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian/apt.systemd.daily, branch 1.2.10</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.2.10</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.2.10'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-04-01T11:02:39Z</updated>
<entry>
<title>Use systemd.timer instead of a cron job</title>
<updated>2016-04-01T11:02:39Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@ubuntu.com</email>
</author>
<published>2016-03-17T07:56:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=14669d4b95f0f6a9b215d7fa5aebbc3b7198585d'/>
<id>urn:sha1:14669d4b95f0f6a9b215d7fa5aebbc3b7198585d</id>
<content type='text'>
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
</content>
</entry>
</feed>
