I guess we should go to something like OnCalendar=*-*-* 6,18:00 RandomizedDelaySec=1h AccuracySec=1h
or tie down random and accuracy even more. We could do like 15 min or so - the cron job used 30 min sleep maximum. The boot argument with short runtime should be ignored. We can't help everyone. People are already complaining that the job runs during boot and want us to delay it during boot. systemd provides no infrastructure for us to depend on network being available reliably (or well, at all), so that's not optimal either. ** Bug watch added: github.com/systemd/systemd/issues #5659 https://github.com/systemd/systemd/issues/5659 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
