On 19 Mar 21:45, Chris Green wrote:

I am having trouble getting things in /etc/rc.local to run. As I understand it this *should* be the standard way to make local additions to be run at startup.

This is on an Ubuntu 13.10 system runnning on a Beaglebone Black so is maybe a little out of the ordinary.

As I understand it /etc/init.d/rc.local gets run by the system startup process and, if there's anything to be run in /etc/rc.local that will be run. This doesn't appear to be happening.

What init system are you using, would be a good question at this point... upstart/systemd might be skipping /etc/rc.local.

If I run '/etc/init.d/rc.local start' manually then the contents of /etc/rc.local get run and there are no errors. So it would seem that for some reason /etc/init.d/rc.local isn't getting run at system startup.

/etc/init.d/rc.local is obviously sysvinit, but other init systems (may or maynot) execute /etc/rc.local, also check that /etc/rc.local has execute permissions *and* a correct shell defined...

The system runlevel is 2. I'm sure that /etc/rc.local should be run at every run level so I don't see how this could affect it.

That'd suggest sysvinit, erm, which I wouldn't have thought from ubuntu... Without "seeing" the system, it's hard to tell what's wrong, but my guess is that $init_system (potentially upstart) isn't firing off /etc/rc.local. Now interestingly a quick google brings up... http://askubuntu.com/questions/243044/why-isnt-rc-local-executed Which says, move things, set it to not run it, move 'em back, set it to run 'em. Cheers, -- Brett Parker