[systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

[Stephen Gallagher]

On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote:
> On Thu, 30.04.15 08:54, Stephen Gallagher (sgallagh at redhat.com) 
> wrote:
> 
> > Does set-linger persist across reboots? 
> 
> Yes it does. When a systemd is booted up with a user that has
> lingering on this means that his user at .service instance is invoked at
> boot, without waiting for any login.
> 

One last question, Lennart: what is the primary use-case for the
linger feature? When is it expected that users would want to use it?
We (SSSD) need to make sure we have it tied to the right set of access
rights. At the moment, we're defaulting it to "Allow". If this is
expected to be useful only for running automated tasks when the user
isn't logged in, we should probably associate it with that set of
access rights instead of blindly allowing it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150430/c872be7e/attachment.sig>