Assuming s6-rc is used for the main supervision tree and on login, which is fair, since the very thing we discuss about is part of my project doing all of that with s6-rc, this would cause users to need to learn s6 additionally to s6-rc, when s6-rc can be used for all cases.The vast majority of services a user will want to have are longruns. And longruns are run under s6; longrun service definition directories are pretty much s6 service directories. I don't think it's honest to say "you only need to learn s6-rc, not s6"; the s6-rc learning curve *includes* learning at least the fundamentals of s6.
As a matter of fact, I’ve setup “user services” on my computers (services for one user only actually, I do not care about edge cases since I’m both root and the regular user) a few months ago with s6-rc, and up til now I only have longruns.
I do have though dependencies between these longruns, mostly between the user dbus service and other user-specific services that depend on that thing, like pipewire.
Not sure it would justify the use of s6-rc, because one could just let pipewire start and die until dbus is run. Or consider these services do not make sense when the user is not logged in, so that they will be run by s6-rc on login.
Hoël
signature.asc
Description: PGP signature
