Hi It seems I answered my first question seems setting --setenv=XDG_SEAT=seatx and that will cause pam_systemd.so to set the session-seat to what the variable is set to. While the documentation says that pam_systemd.so can _set_ to the variables, it wasn't clear that it also _responds_ to what they are set to.
I still have my other question, is it possible to set CanMultisession to yes on other seats besides seat0? Thanks On Saturday, July 29, 2017 12:34:46 AM EDT nerdopolis 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? > > > > Thanks > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
