Unfortunately for us, systemd provides no good interface to improve
things. There's the ability to wait on network, but AFAIUI that does not
really help much, as it does not deal with resume. Also waiting on the
network could time out, and the service would then be marked as failed
and also run 12 hours later.
The best solution would be to have a service that runs while the machine
is online and that other units can bind to: Then you could bind the
timer (!) to the online-ness of the system.
That said, Wants=network-online.target and After=network-online.target
or similar are probably better than nothing.
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667769
Title:
apt-daily.service running too early in boot process
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1667769/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
