On Sat, Aug 29, 2015 at 5:52 PM, ToddAndMargo <[log in to unmask]> wrote: > On 08/29/2015 02:18 PM, Jim Campbell wrote: >> >> To get systemd to start something at boot, you enter: >> >> systemctl enable foo > > Not on this one. But it is working now anyway, so go figure. > > # systemctl enable rc-local > The unit files have no [Install] section. They are not meant to be enabled > using systemctl. > Possible reasons for having this kind of units are: > 1) A unit may be statically enabled by being symlinked from another unit's > .wants/ or .requires/ directory. > 2) A unit's purpose may be to act as a helper for some other unit which has > a requirement dependency on it. > 3) A unit may be started when needed via activation (socket, path, timer, > D-Bus, udev, scripted systemctl call, ...). /usr/lib/systemd/system-generators/systemd-rc-local-generator creates a symlink from /run/systemd/generator/multi-user.target.wants/rc-local.service to /usr/lib/systemd/system/rc-local.service The above unit includes the following line ConditionFileIsExecutable=/etc/rc.d/rc.local So /run/systemd/generator/multi-user.target.wants/rc-local.service will be enabled in the multi-user runlevel if /etc/rc.d/rc.local is executable (it works for me if its mode is 744 so I don't understand why you need 755)