On Thu, May 18, 2017 at 5:02 PM, Luis Ressel <aranea_at_aixah.de> wrote:
> >
>
> Yes, when your init exec's into s6-svscan, it will immediately start all
> >
>
> services in the scandir (unless the corresponding servicedir contains
> >
>
> a down file).
> >
>
> >
>
> However, the scandir will typically be empty at this point (it may
> >
>
> contain an early getty service). It is only populated with services
> >
> o
> nce you call s6-rc-init (to be exact, s6-rc-init creates the
> >
>
> servicedirs in /run/s6-rc/servicedirs and then symlinks them into the
> >
>
> scandir). s6-svscan will still not start the services, though, since
> >
>
> all the servicedirs created by s6-rc-init will contain a down file.
> >
>
> They will only be started once you call s6-rc -u change ok-all (ok-all
> >
>
> being the s6-rc bundle containing all your services).
>
Ah, I see my error was assuming that scandirs were static for the life of
the current boot, rather than having service directories symlinked in.
Thanks for the help.
Received on Fri May 19 2017 - 14:22:22 UTC