Hi, I'm looking at clean solution how to create additional seat for standalone, self-contained X server (one X server per seat, X server does not rely on any physical hardware). Such X server are xvnc or Xspice. I could find a dated howto for such a configuration: http://zeusville.wordpress.com/2012/01/27/setting-up-vncserver-on-fedora-16/ and two oldish related bugs from time of logind transition: https://bugzilla.redhat.com/show_bug.cgi?id=896648 https://bugzilla.redhat.com/show_bug.cgi?id=988030 some 10000ft overview of multi-seat with systemd-logind: http://www.freedesktop.org/wiki/Software/systemd/multiseat/ and it's detailed dbus interface: http://www.freedesktop.org/wiki/Software/systemd/logind/
What I miss is a general overview of how should things work together. More specifically: 1) How to define other seat that uses another X server? IMO it should be necessary to define that just in .service file because X servers like Xspice don't need other inputs or outputs than those they do provide for themselves 2) How can *dm fit for servers running in such seat > 0? If they are seat-aware, can they learn their seat information just from the environment? 3) (not sure if in systemd (logind?) scope) is it possible to block multiple graphical logins for a single user? I'm afraid that DE's and desktop applications arent written generally in a way that would allow concurrent sessions of the same user so it should be blocked 4) could systemd somehow allocate DISPLAY variables and/or network ports? It would make sense to run these services instantiated and systemd as a service manager seems to be the natural fit This would be just a beginning but let's see if it is possible to create such network seats using systemd David PS: please keep me, Jeremy and Alon in CC, we're not subscribed to the list. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
