On Tue, Apr 25, 2017 at 08:16:37AM -0000, Julian Andres Klode wrote: > We can't increase the delay for older distros, as it delays all daily > cron jobs there. We could increase to 2 hours, but I don't feel like > doing daily APT releases changing time outs, and 1.4.1 with the 1 hour > time out is out already. >
For older distros where apt daily still happens from cron (and not systemd timers), we could rename /etc/cron.daily/apt to something like zzapt so it happens at the very end so it doesn't delay all daily cron jobs. Then ship out /etc/apt/apt.conf.d/50unattended-upgrades overriding APT::Periodic::RandomSleep (3600) so it's easier for users to override if needed. > I mean, I change it to 2 hours now, and tomorrow someone else turns up > and either says 2 hours is too much or 2 hours is too low. Or not "5 to > 7, I'd rather have 6 to 8." I think at some point we have to stay with a > decision. > > If 1 hour turns out to be problematic, then we should revisit this when > we see an issue IMO. Okay. Thanks, Haw -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
