Bug#946645: KillUserProcesses=no disregarded for some cgroups

[Michael Biebl]

Am 10.02.20 um 16:29 schrieb chrysn:
> On Mon, Feb 10, 2020 at 03:04:49PM +0100, Ansgar wrote:
>> If I start an xterm via Alt-F2 in gnome, the xterm process runs in a
>> cgroup like gnome-launched-xterm-489694.scope.  gnome-terminal or an
>> xterm started in gnome-terminal run in the gnome-terminal-
>> server.service cgroup.  I expect openbox doesn't do this and processes
>> started by openbox run in the same cgroup as openbox itself.
>>
>> `systemd-cgls` is useful to see how processes are organized into
>> cgroups.
>>
>> The gnome-launched-*.scope has KillMode=control-group, so all processes
>> including background processes like tmux get killed when the unit gets
>> stopped (systemd --user show -p KillMode gnome-launched-....scope).
> 
> That does not explain the on-and-off behavior, but helps in
> understanding why processes get killed in the first place.
> 
> Then, however, is KillUserProcesses completely obsolete? A user trying
> to debug a situation like mine will currently wind up in the discussion
> of #825394 and look into KillUserProcesses' documentation. Even if it's
> not completely obsolete, a warning that desktop environment spawned
> processes might also be subject to killing from their desktop
> environment's KillMode would be helpful.

Maybe we should first get to the bottom of your issue before jumping to
conclusions and producing incorrect/incomplete documentation.

Michael


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200210/558dc13a/attachment.sig>