El vie, 24 abr 2026 a las 15:04, kurth4cker escribió:
>
> tmux will be started at user login. It is not river session specific.
> beansprout, gammastep and foot are all depend on $WAYLAND_DISPLAY which
> is determined and set by river at startup. Currently river starts a
> specific s6-svscan tree whenever it starts. So environment is passed to
> all tree and this programs.
And "user login" does not happen at the same time as starting River
(like with a Wayland session-capable display manager)? If no, how is
tmux started then if there's no supervision tree created by River's
startup scripts yet? The other message shows a tmux process in the
same supervision tree as those that need a Wayland display socket, so
it must have been started by River even if it does not use its
socket...
Also, not related to service management itself, but you also described
in another message starting two instances of River, how does that
work? Isn't only one single compositor driving the display at any
time? What do you use the other instance for? (I don't have Wayland
setups myself.. yet).
And, out of curiosity, may I ask what operating system are you testing
all of this on :) ?
G.
Received on Fri Apr 24 2026 - 21:43:09 CEST