From 14669d4b95f0f6a9b215d7fa5aebbc3b7198585d Mon Sep 17 00:00:00 2001 From: Michael Vogt Date: Thu, 17 Mar 2016 08:56:58 +0100 Subject: Use systemd.timer instead of a cron job 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 --- debian/apt-daily.timer | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 debian/apt-daily.timer (limited to 'debian/apt-daily.timer') diff --git a/debian/apt-daily.timer b/debian/apt-daily.timer new file mode 100644 index 000000000..037f00e24 --- /dev/null +++ b/debian/apt-daily.timer @@ -0,0 +1,11 @@ +[Unit] +Description=Daily apt activities + +[Timer] +OnCalendar=*-*-* 6:00,18:00 +RandomizedDelaySec=12h +AccuracySec=1h +Persistent=true + +[Install] +WantedBy=timers.target -- cgit v1.2.3