We hope you are enjoying an excellent Christmas break and wish you a Happy New Year! OSMC's December update is primarily a maintenance release. We have fixed a number of bugs and have introduced some small improvements.
I have some scripts I launch from rc.local. After this upgrade, I noticed they now fail with network problems. I guess it has something to do with network state when rc.local is triggered (i.e. must now launch before network connection is ready, while this was never a problem before). Anyways, solved this by undoing your good work by putting in a manual delay sleep 10,
Performance tunables are now definable at a per-device level as well as the existing OSMC userland level. This means that we can set some global tunables and override them specifically for Pi 1 and Pi 2 depending on the device for some more fine tuned workloads.
rc.local is not synchronised to the network going up in any way - on my systems rc.local has always run before the network is up. It waits until the network manager starts, but not for the network to actually go up.
If you want to run services after the network is up your best option is to enable “wait for network” in the networking GUI, then create a systemd service to run your scripts, and specify:
@DBMandrake this is very interesting - thanks for sharing!
I did not think rc.local was synchronized to the network status. It’s just that the boot time sequencing always worked out before (by luck, I suppose), and immediately after the December update the scripts failed every time with network errors. So the boot timing must have changed, at least on my Pi (i.e. the network is now coming up later than it was before)?
Slowing down rc.local with sleep=10 “solved” the problem. But obviously that is an ugly hack, so I will gladly try your suggestions in order to learn something new.
Just a note- the update to Samba required keyboard input during configuration, but I don’t have a keyboard or easy physical access to the Pi. I had to SSH in and run apt-get upgrade and then do the update through OSMC. I was afraid to run dist-upgrade on its own.
However, I already had problems with Airplay before (irregularities when playing music, dropped connections, etc.), but now it doesn’t play anything anymore! For me, Airplay was the most important feature of OSMC/Kodi, so I was hoping it would work flawlessly when I decided not to go for an AppleTV.