[systemd-devel] seat > 0 provided by standalone X server (Xspice, xvnc)

[Lennart Poettering]

On Tue, 01.04.14 15:31, David Jaša (djasa at redhat.com) wrote:

> 
> 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:

The "seat" concept exposed by logind is about device management. Thus,
for virtual sessions like ssh, xvnc, xspice the concept does not apply
at all, because they don't need access to any physical device. 

Sessions in logind are either attached to a seat or not. Virtual
sessions are not.

Lennart

-- 
Lennart Poettering, Red Hat