'Twas brillig, and David Herrmann at 01/12/13 11:43 did gyre and gimble: > During session_load() or if two sessions have the same VTnr, we may end up > with two sessions with the same position (this shouldn't happen, but lets > be fail-safe in case some other part of the stack fails).
I presume this would actually be quite easy if we get around to implementing Lennart's suggested force-new-session=1 pam_systemd option which will be used by su-l, sudo-i, and possible polkit stuff? > This case is > dealt with gracefully by ignoring any session but the first session > assigned to the position. Thus, session->pos is a hint, seat->positions[i] > is the definite position-assignment. Always verify both match in case you > need to modify them! Even if pam_systemd did get this new feature, it sounds like this strategy would work fine for dealing with switching anyway. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
