> - What's the best approach to setup s6-rc?
That's... a complex question, because it depends on a lot of parameters.
What is your context? what is your environment? How have you set up
your machine so far? etc.
> - I see this tool http://skarnet.org/software/s6-linux-init/ for init
> creation. Is this the right direction?
s6-linux-init is a shortcut to help people run s6-svscan as process 1
with a catch-all logger: it simply automates the difficult task of
writing a stage 1 init. It does not write your stage 2 for you -
which is where s6-rc would get involved.
You can use s6-linux-init if you wish, but if you have already manually
done the work of setting up a s6 infrastructure with s6-svscan running
as process 1, you probably don't need to.
In order to use s6-rc, what you need to do is 1. analyze your current
boot process: what services are started, what is a one-shot and what
spawns a daemon, what are the dependencies between those steps.
2. write a set of definition directories, in the s6-rc source format,
that represents those services and their dependencies. 3. compile that
set via s6-rc-compile. 4. change your stage 2 init into something akin
to "s6-rc-init && s6-rc change my-runlevel", if "my-runlevel" is a
bundle representing all the services you want to have at boot time.
--
Laurent
Received on Thu Feb 25 2016 - 13:57:23 UTC