@davidgoodchild wrote:
My problem is that I don’t know which file or directory it can’t find – as far as I can see, I have created all that needs to be created and given read (or write where needed) permissions to ‘nobody’…
My guess would be that your init.d script doesn’t match the actual location of the binary. For example, the init.d script is trying to launch /usr/sbin/mt-daapd, but you configured mt-daapd without a “–prefix=/usr”, putting the binary in “/usr/local/sbin”.
See if that’s the case. Does the mt-daapd binary actually exist where the init.d thinks it is? In /usr/sbin?