[systemd-devel] pam_systemd closing user's session prematurely
Ray Strode
halfline at gmail.com
Tue Oct 16 13:27:24 PDT 2012
Hi,
On Tue, Oct 16, 2012 at 2:20 PM, Lennart Poettering
<lennart at poettering.net> 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?
> Thanks for tracking this down and for your patch!
Well, Owen Taylor tracked it down actually.
> Please test!
Will do.
--Ray
More information about the systemd-devel
mailing list