Separating out u-u from the rest of the apt maintenance script could be useful, but I prefer running the update, package fetch, upgrade then cache clean up all in one hit. You *can* delay your reboot time, but the shutdown command, at least pre-systemd would run until the shutdown happens, periodically issuing a message to all terminal users before stopping further logins and finally changing the runlevel to reboot the machine. Less than ideal in the old cron.daily days, as those jobs run sequentially and in lexical order. And a is for apt.
In the mixed jessie, trusty, xenial environment we run, we've moved to taking the apt job out of cron.daily entirely, running the reboot 'now', and using the cron/timer start time to effectively schedule the reboot. My grievance is mainly that in making the transition to systemd the upstream developers chose to: 1) Significantly change the job start time behaviour 2) Not bother to mention this behaviour change in the the changelog It would be good to see Ubuntu at least set the timer defaults in such a way that enabling unattended upgrades doesn't result in nasty reboot during the day default behaviour. Which, given the half hour random start time default, should be achievable without putting undue load on the servers. -- 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: Triaged 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 : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
