On Tue, Oct 16, 2012 at 04:27:24PM -0400, Ray Strode wrote: > Hi, > > On Tue, Oct 16, 2012 at 2:20 PM, Lennart Poettering > <[email protected]> wrote: > > I have now commited a fix that achieves the same as yours but doesn't > > key this of the static service database: I simply extended the > > OpenSession() bus call to inform clients whether they are a new session > > or just got the previous data returned. With that boolean we can then > > later do or skip the unrelease and should be safe. Adding this > > OpenSession() seemed like the cleanest way to pass this information to > > pam_systemd, and should be without risk, since we never included > > OpenSession() in any docs, as we consider it a private API. > Cool. Though, won't this break logins after logind is upgraded until > reboot? Or does logind get restarted on package install?
Aparently a reboot is not needed, but 'systemctl restart systemd-login.service' is. Oct 16 21:43:14 fedora-15 sshd[12846]: pam_systemd(sshd:session): Failed to parse message: Message has only 5 arguments, but more were expected Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
