Laurent Bercot schrob: > An objective fact is that both OpenRC and systemd always address > system services by default, and need an explicit --user to address user > services, even when invoked with uid != 0. > My question was, is it more natural to do it this way, or does it make > more sense for normal users to access their own user service database by > default (since they cannot modify system services anyway). > Some people say that users access the system services more anyway, > almost never touch user services, and want consistent behaviour no matter > their uid, so the OpenRC way of doing it is better. > Others say that my initial inclination is right and "s6 foobar" should > mean the user service by default unless invoked as root.
While I have no opinion on the "default default" behaviour (of s6
without either --user nor --system), I would wish it to be configurable
by an envirionment variable, analogous to runit's SVDIR. That way, users
can set it to whatever they prefer and configure sudo to strip (or add)
it, and then plain "s6" will always default to that particular user's
choice.
... without requiring an extra /usr/local/bin/s6 wrapper doing
just that, which would be a likely outcome if I were to use an s6
without that feature:
On my servers, sv defaults to system services, because my
dont-login-as-root account has no need of user services. My desktop at
work runs systemd+runit-run, thus sv defaults to user services, because
there are no system services other than unprivileged.$USER . My private
pc has both system services and user services, and I occasionally end up
in the wrong SVDIR. ;)
cheers,
Jan
signature.asc
Description: PGP signature
