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
