Hello,
El vie, 13 mar 2026 a las 16:44, Carlos Eduardo escribió:
>
> Wanted a refresher on how to set up s6 instanced services with s6-rc, but
> the s6-rc-compile documentation reads:
>
> > Optional directories named instance and instances. These will be copied
> verbatim into the generated service directory. They are used internally by
> some s6 tools; using them for your own purposes is not recommended - you
> should ignore them and use the data directory instead.
>
> Does this mean using the s6 instances feature is not recommended?
That's not how I interpret that quote. I read that as: "a longrun
definition can contain 'instance' and 'instances'; if it does, they
will be copied verbatim, but don't put arbitrary stuff in those
directories; it you want a place for arbitrary stuff that you want
copied verbatim to the service directory, use 'data' instead".
> Are there plans to revamp the source format for templated services?
I'm not sure what you are asking here, but if you mean "can we use
both s6-rc and instanced services", then, as I understand it, the
answer is "yes": 's6-instance-maker -r foo tpl dir' will create, as a
subdirectory of 'dir', a longrun definition for an instanced service
using template 'tpl', and the service will be named 'foo'. Directory
'dir' can exist in this case, and can contain other service
definitions already.
Then one can pass 'dir' to s6-rc-compile, start the service with
's6-rc start foo' once the compiled database is live, and create
instances with 's6-instance-create ${scandir}/foo instance_name' when
the service is up.
G.
Received on Sat Mar 14 2026 - 03:26:28 CET