[Bug 1468103] Re: rc.local runs earlier than cloud-init.service
** No longer affects: systemd (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
[Bug 1468103] Re: rc.local runs earlier than cloud-init.service
As I explained, the notion of "the last thing during boot" is not well- defined with a partially ordered and parallel init system like systemd or upstart (or even sysvinit+startpar). So as long as cloud-init.service declares itself to run after rc- local.service, then rc-local.service necessarily can't be "the" last thing even accidentally. This is something to decide in cloud- init.service. ** Changed in: systemd (Ubuntu) Importance: High => Undecided ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- 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
[Bug 1468103] Re: rc.local runs earlier than cloud-init.service
Independent of cloud-init, things in rc.local should be run as the last thing in boot. So now we have last thing except cloud-init :-) There are other services which order themselves after it, like getty@, plymouth-quit and others, to avoid disturbing init.d/rc.local scripts with allocated VTs or plymouth going away. This was more or less the same case with upstart. But nevertheless it should run at least after the init.d scripts (and their unit counterparts), to maintain backwards compatibility with that. This still isn't robust (if you need to run after something it's always correct to actually declare it), but might help in some situations. ** Project changed: hundredpapercuts = systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Confirmed = Triaged -- 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
