> > > However, i have a another trouble, when i try to launch some classic
> > > service with the second scandir(or the first, it's equal) i have this
> > > error on the log : _at_40000000575cf0bb05fd2e24 s6-supervise
> > > syslogd-linux/log: warning: unable to spawn ./run - waiting 10
> > > seconds _at_40000000575cf0c504c9de44 s6-supervise syslogd-linux:
> > > warning: unable to spawn ./run - waiting 10 seconds
> > > _at_40000000575cf0c504ca5f2c s6-supervise (child): fatal: unable to exec
> > > run: No such file or directory _at_40000000575cf0c50660c63c s6-supervise
> > > (child): fatal: unable to exec run: No such file or directory
> >
> > You have an invalid "syslogd-linux" service directory, with no run script.
> > Same thing with syslogd-linux/log. Check what is happening to your run
> > scripts.
>
> i taken your original service from your s6 package, i do not have changing anything on it appart the s6-setuidgid at the log scripts that i defined with s6log according to my system. However, if i try with your klogd-linux service, the error is equal. So, this is the procedure i use, perhaps i make a mistake :
>
> i copy the entire directory syslogd-linux to my running scandir /run/boot/service
> then i enter this command on the console:
> s6-svscanctl -an /run/boot/service
shame on me :(, i forgot to change the shebang according to my system, all works fine here, sorry for that
--
Eric Vidal <eric_at_obarun.org>
Received on Mon Jun 13 2016 - 15:06:52 UTC