[systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

Colin Guthrie colin at mageia.org
Fri May 1 01:46:26 PDT 2015

Stephen Gallagher wrote on 30/04/15 14:04:
> 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?

There are lots of potential uses.

e.g. a user may want to run their irssi IRC client at all times
(connecting into it via screen or via proxy etc).

Or maybe they want to run Rygel to export their media collection over
the network. Various other daemons make sense to be run in a per-user
context (i.e. not system services) and the lingering feature allows this
in a clean way.

Hope this gives you some use cases. I'm sure other people an give others.



Colin Guthrie

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

More information about the systemd-devel mailing list