Re: Re Adding mdevd
The exact message is 's6-supervise mdevd: warning: unable to spawn ./run ( waiting 60 seconds): No such file or directory Yes, it's a message from s6-supervise. As indicated by the first word. 🙂 The only new services added are mdevd and init-coldplug, copied from the examples in the s6-rc source. Check the run script of your mdevd service. Chances are the shebang does not correspond to the path where you installed your execlineb binary. -- Laurent
Re Adding mdevd
The exact message is 's6-supervise mdevd: warning: unable to spawn ./run ( waiting 60 seconds): No such file or directory The only new services added are mdevd and init-coldplug, copied from the examples in the s6-rc source. Thanks for the prompt reply and sorry for this disjointed conversation; I can read your reply online but have not recieved them as email as yet.
Re: Adding mdevd to the s6 boot process
Mdevd now warns 'unable to spawn ./run' every 60 seconds. That sounds like something s6-supervise would write, not mdevd. Are you sure it's related to mdevd? Check the service directories you just added. Any hints as to what ./run it is trying to run and where it should be? Typically it's the starting script of a longrun service, located in a service directory. We'd need the full, exact error message to be more precise - the relevant information is in what you didn't say. -- Laurent