On Mi, 29.07.20 00:11, nerdopolis (bluescreen_aven...@verizon.net) wrote: > Hi > > Sorry about the length. > > I have a unique thing I am trying to solve, is that if I have a service that > calls /sbin/logind under > something like tmux, and I set `Environment=XDG_SEAT=seat0` in the service > file, upon logging in, > pam_systemd fails to create a session, as it's seat0 and it's expecting a > valid TTY number, as it's > seat0. One of the side effects is that you lose the credential prompt that > you usually get if you > run a command like `systemctl restart foo.service`, and there could be other > things too?
Seats are a concept of grouping hardware. A seat without hardware is pointless. If you have no hardware associated with a session then the session is seat-less, which is totally fine. I don't get what you are trying to do? Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
