rc.local is enabled, and part of the initial boot target... if it
exists, and is executable.
Can you please provide steps, or details of your system, on which you
observe that it was not executed on boot? when present, and executable?
Note by default on ubuntu, there is no rc.local shipped. But would be
used, if there is one on boot.
# cat /etc/rc.local
echo Hello rc.local
# sudo chmod +x /etc/rc.local
# sudo reboot
# journalctl -b -u rc-local.service
-- Logs begin at Thu 2018-05-17 13:22:46 UTC, end at Thu 2018-05-17 13:24:28
May 17 13:23:39 test-rclocal systemd: Starting /etc/rc.local Compatibility...
May 17 13:23:39 test-rclocal rc.local: Hello rc.local
May 17 13:23:39 test-rclocal systemd: Started /etc/rc.local Compatibility.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
enable rc-local.service unit by default
Status in systemd package in Ubuntu:
Every other systemd-infected distribution leaves the rc-local.service
unit enabled; this is probably because provisioning systems need to
use it to launch first-boot tasks.
Ubuntu has been blindly following suit in every other respect and
should do the same here also. It's a null op unless the file exists
and is executable, so enabling it gives all the benefits for extremely
Example reproducable bug:
* preseed a new host and an rc.local expected to run on boot
* boot and realise rc.local didn't run
* realise you can't enable it in the preseed as systemctl is not affecting
the target system
* curse Lennart (again) and run Devuan instead where things just work as they
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp