> Generally speaking people expect rc.local to be run as "the last thing in boot".
This can't be taken literally, as services can and do come and go (stop and start) all the time, and as any service can declare dependencies to run after "your thing" this can't be enforced either. For example, could-final.service has an "After=rc-local.service" which I assume is deliberate. So we can't do a thing like "run rc-local.service after multi-user.target" as that would be an unresolvable ordering with cloud-final.service. Thus I suggest to add an After=rc-local.service to cloud-init.service. This is explicit and unambiguous. ** Summary changed: - rc.local runs too early. + rc.local runs earlier than cloud-init.service ** Package changed: systemd (Ubuntu) => cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1468103 Title: rc.local runs earlier than cloud-init.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1468103/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
