Re: Re: Systemd migration: opinion and questions

Am Wed, 25 Feb 2015 14:31:55 -0500
schrieb Rich Freeman <[email protected]>:

> On Wed, Feb 25, 2015 at 2:17 PM, Marc Joliet <[email protected]> wrote:
> > Am Wed, 25 Feb 2015 10:33:37 +0000 (UTC)
> > schrieb Duncan <[email protected]>:
> >
> >> But you're king of your own boxes.  If you want to run it as a user-level
> >> service and have it quit when you logout that user, go right ahead.
> >
> > Again, it *doesn't* terminate when I log out.
> 
> FYI - this behavior is completely configurable - you can enable or
> disable linger for any particular user.

Ah, then the *-linger commands to loginctl are related to this?  However,
loginctl says:

    % loginctl show-user 1000
    UID=1000
    GID=100
    Name=marcec
    Timestamp=Mi 2015-02-25 18:36:59 CET
    TimestampMonotonic=11724536
    RuntimePath=/run/user/1000
    [email protected]
    Slice=user-1000.slice
    State=active
    IdleHint=no
    IdleSinceHint=0
    IdleSinceHintMonotonic=0
    Linger=no

Hmm, one more thing to look this up, I guess.

Ah, I think I found it: I think it's the KillUserProcesses option
in logind.conf(5), which defaults to "no";

    KillUserProcesses=
        Takes a boolean argument. Configures whether the processes of a user
        should be killed when the user completely logs out (i.e. after the
        user's last session ended). Defaults to "no".

Perhaps I'll explicitly configure that, just so an upgrade doesn't accidentally
break things.

Ah, and looking at loginctl(1) now I understand what linger means: it lets you
start systemd user sessions at boot, without having to log in (so I was wrong
in the MPD sub-thread).  Nice!

[...]

Greetings
-- 
Marc Joliet