> 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
Server Team, which is subscribed to cloud-init 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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
