[systemd-devel] Socket is dying, how to automatically restart it?

[Lennart Poettering]

On Thu, 18.04.13 16:38, Thomas Bächler (thomas at archlinux.org) wrote:

> Am 18.04.2013 16:04, schrieb Lennart Poettering:
> > That said, screen should probably set up a new PAM session of its own
> > and detach from the original one.
> 
> That sounds like a good idea - unfortunately, screen does not seem to
> have PAM session support at all, and I couldn't find the obvious place
> to add this inside screen (I didn't invest much time in it either). This
> would allow screen sessions to be tracked by logind instead of having
> many "State=closing" sessions floating around.

BTW, this probably needs sokme changes in systemd too. Since right now,
if you open a PAM session from a process that is already part of a PAM
session logind will just return the same data as the first time. So to
make this work properly, we'd to define a way how certain PAM services
can explicitly ask to get a new session assigned.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.