Bug#989317: systemd kill background processes after user logs out (#825394 regression)

[Michael Biebl]

Am 08.06.2021 um 18:08 schrieb Matt Corallo:
> Hmmm, with set-linger and --scope I can't seem to reproduce now either, 
> its possible I had forgotten the --scope at some point while testing 
> set-linger before, sorry for the noise here.
> 
> Still, based on my read of #825394, it seems like it should be the case 
> that you do not need set-linger and the default behavior should be that 
> things aren't automatically killed in the background? Is that something 
> that was an intentional change?

Change to what exactly?

I guess we need to differentiate between login and user sessions.
It's my understanding that KillUserProcesses= only affects a login session.

If you start a process as part of a user session (which is what 
systemd-run --user does), ending that user session will stop that process.

> The systemd-run manpage seems to indicate that with debian's default 
> change of KillUserProcesses=no this should not occur with or without 
> linger. In either case, it seems the manpage should be updated to 
> describe this behavior, and maybe updated to mention that 
> KilUserProcesses is *not* the default on Debian, which it states in the 
> EXAMPLES section.

We had this discussion in the past. The man pages document the upstream 
default behaviour. Patching all man pages to reflect Debian specific 
changes is unfortunately not maintainable. Sorry.

Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210608/89cae8f8/attachment.sig>