Re: s6 instanced services are "forgotten" after s6-rc-update

From: Carlos Eduardo <carana2099_at_gmail.com>
Date: Sat, 28 Jan 2023 22:09:13 -0300

Yes. I'm using s6 2.11.2.0 and s6-rc 0.5.3.3.

I can provide an strace of s6-rc-update if needed. Looking into it, it
seems s6-rc-update "uncritically" unlinks the live instance/ and instances/
folders and replaces them with brand-new copies from the compiled database.

Em sáb., 28 de jan. de 2023 20:16, Laurent Bercot <ska-skaware_at_skarnet.org>
escreveu:

>
> >After having an instanced service definition for s6-rc, subsequent
> >calls to s6-rc-update seem to clobber the instance/ and instances/
> >subfolders in a way that keeps the instances running, but makes it
> >impossible to control them.
> >
> >After s6-rc-update, I get error messages like:
> >
> >fatal: unable to open /run/service/agetties/instance/.s6-svscan/lock:
> >No such file or directory
> >fatal: unable to control /run/service/agetties/instance/tty1: No such
> >file or directory
>
> Hmm, that's weird. Are you sure you're using the latest s6-rc version?
> Only 0.5.3.3 will correctly manage instances.
>
> If you are, I'll try to reproduce the issue to understand what's going
> on.
>
> --
> Laurent
>
>
Received on Sun Jan 29 2023 - 02:09:13 CET

This archive was generated by hypermail 2.4.0 : Sun Jan 29 2023 - 02:09:55 CET