[systemd-bugs] [Bug 67288] console login no longer possible when PAM_SESSION_ERR condition is triggered

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=67288

--- Comment #5 from Michael Stapelberg <michael+freedesktop at stapelberg.de> ---
(In reply to comment #4)
> (In reply to comment #3)
> > I propose changing the code so that it won’t close the file descriptor at
> > all. Even though sessions will pile up and not work as expected, you will
> > still be able to log in, which is important. What do you think?
> 
> Does logind provide an API which allows one to tear down a session without
> killing all its processes?
>From looking at http://www.freedesktop.org/wiki/Software/systemd/logind/ I
would say no, it does not.

Also note that the code path we are talking about is entered (amongst other
conditions) when the code cannot talk to logind, so depending on logind for the
error handling seems wrong :).

Lennart, Kay, what do you think with regards to comment #3?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130728/6f359657/attachment.html>