From 6267b47f85588fdd00f6e667598abe52887385ae Mon Sep 17 00:00:00 2001 From: Julian Andres Klode Date: Fri, 21 Apr 2017 21:18:59 +0200 Subject: systemd: Rework timing and add After=network-online The timeout values were so large that the timer could run at any random time of the day, possibly easily interfering with business hours, and causing trouble. Reduce them to 30 minutes of random delay and an accuracy to the default value (1 minute). Also drop the 18:00 event. People still actively use their device during that time, and for servers, there might be less attendance than in the regular 06:00 time slot, so longer time to fix things if something breaks. During a boot, the service might be run to catch up with a timer that would have normally elapsed. Due to no dependencies, it would have run before the network is online - that's bad. Adding an After and a Wants fixes that for boots, but still leaves the same issue for Resume. LP: #1615482 (cherry picked from commit b4f32b13055287d2ac46a08255db475af195b5f7) --- debian/apt-daily.timer | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/debian/apt-daily.timer b/debian/apt-daily.timer index a8e182c85..8ac13b0e9 100644 --- a/debian/apt-daily.timer +++ b/debian/apt-daily.timer @@ -1,10 +1,11 @@ [Unit] Description=Daily apt activities +After=network-online.target +Wants=network-online.target [Timer] -OnCalendar=*-*-* 6,18:00 -RandomizedDelaySec=12h -AccuracySec=1h +OnCalendar=*-*-* 6:00 +RandomizedDelaySec=60m Persistent=true [Install] -- cgit v1.2.3