It was <2013-11-25 pon 14:49>, when Łukasz Stelmach wrote: > It was <2013-11-25 pon 13:46>, when Hans de Goede wrote: >> Hi Łukasz, > > Hello, nice to ... meet you :-) > >> I'm a new member of Red Hat's graphics team. At the request >> of Peter Hutterer I've been looking at your systemd socket >> activation patches. >> >> Applying / building them was not a problem. >> >> My initial thought for testing socket activation was to >> write the necessary unit files and patch gdm to not start >> X for local displays. But the latter bit is much harder >> then it sounds. >> >> Typically the display-manager will start X with a --auth >> parameter passing a file with auth-cookies in there. When >> using socket based activation this won't work. We may be >> able to work around this, but I wonder if it is worth >> the trouble. >> >> Which has left me wondering what the use-case is for this, >> and how you envision socket activation working for X in >> a traditional Linux desktop setup with xdm/gdm/kdm ? > > I work for Samsung, me and my teammates are preparing Tizen. Tizen's not > quite traditional Linux system and it is a single-user system at the > moment (at least the mobile profile). This will probably change and we > will use some kind of dm but not yet. Even when we do so we might want > some more programmes to connect X during boot. > > We've got the DISPLAY variable set to :0 for the entire user session > (managed by systemd --user) and a few other processes. With these > conditions in mind running X as a simple socket-activated service > without a display manager is the simplest option for us. > > For more traditional setups one might try using systemd-run to create > the service to be activated. Yet another
... option is to create a wrapper/rewrite a display manager so they can be started upon connection to the socket and exec*(2) Xorg. -- Łukasz Stelmach Samsung R&D Institute Poland Samsung Electronics
pgpunTw1Z7rMw.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
