On Wed, 31 Oct 2018 11:32:45 +0100 Jérémy Rosen <jeremy.rosen@xxxxxxxx> wrote: > socket-activated weston ? > > nice :) > > Why does weston require logind ? I work in the embedded world and we > usually disable logind entirely (no users in the "human user" meaning of > the term) That's when you run Weston as a normal user: logind grants access to DRM and input devices and revokes access as well when appropriate. Of course, you can work around that by fiddling with device permissions or using some other service that sets those up, and there is weston-launch as well, but logind is really the easy and recommended way to let it work especially on desktop systems. logind is not a hard requirement. That option has usually been called for by people who don't have systemd at all. I'm not sure Weston has ever been tested on systemd but without logind. Or maybe it works and no-one told upstream. :-) Weston actually has three "launchers": one uses logind, one uses weston-launch (a setuid-root helper), and one uses neither. The last one is usually used as root for developer testing, I believe. Thanks, pq
Attachment:
pgpg7imHkHxto.pgp
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
