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.
Both are possible, really. There's nothing that enforces a policy
either way.
When s6-svscan starts, it boots up s6-supervise processes on every
s
On Fri, 19 May 2017 09:22:22 -0500
Robert Hill wrote:
> I see my error was assuming that scandirs were static for the life of
> the current boot, rather than having service directories symlinked in.
Or copied in. Recent s6-svscan won't rescan scandir (aka db) unless you tell
it to.
On Thu, May 18, 2017 at 5:02 PM, Luis Ressel 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 wil
