List of open questions

1. Logind requires PAM to be used anyways so **probably** some PAM module will be used to authenticate a user when he logs in.
2. How exactly multi-seat is done in udev-rules is not clear to me.
3. If anyone can shed light on what some of the more mysterious parameters do please let me know!
4. I am not entirely sure why this is necessary info to the session manager, but it is not entirely weird. Maybe a session created by some PAM module need special handling.
5. How are sessions created that are not user?
6. I don't know what this is for. Remember this is called by the systemd_pam module. Why does that need another way of communicating with logind?
7. since (hopefully) all input device filedescriptors have been handed to the session through logind -> Can we check the cgroups for unassigned ones?
8. "posix sessionids in most cases. But those are not reliable since processes can leave their session and make a new one." Why can we not forbid this to simplify things?
9. "That is why logind pushes the first process into a cgroup right at creation of a session." Is there a naming scheme of the cgroups?

Start by reading the repository material about logind and the references to PAM, udev rules, systemd_pam, sessions, and cgroups. Done means each numbered question has a sourced explanation or is explicitly marked unresolved.

Written by the indexing model from the issue text.