On Sat, Jul 29, 2017, 07:40 nerdopolis <bluescreen_aven...@verizon.net> wrote:
> Hi > > I hope this is the right place to ask this. I have two questions about > logind > and seats. > > First, when I attach a 2nd graphics card to seat1, it seems > CanMultisession is > set to 0. Is there a way to change that? or is that only supported on > seat0, > that supports the TTYs? > > Second, with systemd-run, and maybe a custom '-p PAMName=somepamfile' (if > that > is required), is there a way to spawn a process on seat1 if it exits? > For seat0 sessions, they for instance can be started by specifying > > > -pTTYPath=/dev/ttyX -pStandardOutput=tty -pStandardError=tty > -pStandardInput=tty > > > to systemd-run, which I know only seat0 supports ttys... > I try to do weston --seat=seat1 and it says that seat1 does not match the > session-seat. > Is there a way to start a process with under a specific session-seat? > I haven't experimented much with multiseat, but here might be some things mixed up... tty support is not the same as virtual console support – it's possible to have the former without the latter. AFAIK, only seat0 supports *virtual consoles*, which are currently used for session switching. (For other seats, the kernel doesn't provide a convenient mechanism, and I don't think a replacement method has been implemented yet...) However, StandardInput doesn't need VC switching or anything, just a /dev/tty* device. Unfortunately I'm not sure if the kernel provides even that for other seats :(
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel