Lol. Apologies about the email wrapping. I guess gmail re-wrapped my email after I already wrapped it in the composer. That's annoying
And to correct the record: no AI was used in writing any of my messages. I do not use LLMs to author things. Here I didn't use them to research things either. I was just over-explaining to get the point across, because explaining it succinctly didn't work. And look, it worked! > again, what a display manager needs to do for multi-seat to work. > > This time I'll just refer to the functions you need to call. > > Dude, why did you not start with this? No need for all the rest of the > discussion, I asked how it was supposed to work... > I assumed that you've at the very least read the man pages for the library you're using. Or even just looked at what functions are available in the library you're using. That's step one, before coming to the mailing list. But anyway, I told you about both sd_login_monitor and sd_get_seats in my second email in this thread. That wasn't enough to help you at the time, apparently. FYI, seems all seats would be created at boot not just seat0. Guess AI > missed that. From there, seats could be added or removed, but at the > time seat0 was created, hardware is likely probed in a loop so would > create all seats. > I didn't miss anything here. What you're saying is just inaccurate. For one, your display manager will probably be running before all the seats are finished probing, because GPUs take a long time to probe and systemd is doing everything asynchronously, in parallel. seat0 is special because it always exists, so logind will emit the seat added event when it starts, before the display manager is running. For two, seats can appear or disappear at any time due to device hotplug, like someone plugging in a GPU, or a USB dock, or something like that. FYI, pam is not part of the greeter/client UI, PAM is ONLY invoked as > part of actual login. The pam env is not constructed until after a > successful login. > So you're not using pam for auth. Cool, then it's even easier for you because you don't need to juggle long running PAM worker processes. Anyway I'm glad it has been solved and this thread can end. Best, Adrian
