apt/debian/apt.apt-compat.cron.daily, branch 2.9.0Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.02021-11-03T22:02:41ZUse `command -v` instead of `which`2021-11-03T22:02:41ZVille Skyttäville.skytta@iki.fi2021-11-03T22:02:41Zurn:sha1:48d4b06013ae3d80b95cf72efaf9a5e7468de965
`which` has been deprecated in debianutils 5.0+. The recommended
replacement, `command -v`, is mandated by Debian policy these days, in
addition to being required by POSIX and its predecessor specs at least
since 1994.
Not found commands cause no output from `command -v` per POSIX, so
remove the redundant 2>&1's while at it.
apt-compat.cron.daily: Correctly handle undetermined power status2018-01-10T07:33:41ZJulian Andres Klodejak@debian.org2018-01-10T07:30:25Zurn:sha1:ca2fcc639c7363a04998f650b96573d806b32dd2
If on_ac_power exits with 255 the script would fail at this point
because set -e was set, but it should continue, as 255 means the
power status could not be determined.
LP: #1742378
Use 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
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