Residual processes on the agent after session disconnect

ThinLinc
,
2

Hi @yann28,

Welcome to the forum!

Here’s a response from my colleague @wilsj in regards to a similar query:

This is sadly out of our control. All of these processes are started by
systemd as of starting the desktop environment. Worth noting is that
these processes tend to die all by themselves after a while.

If you still want to get rid of them, there is loginctl disable-linger. There is also the KillUserProcesses option in logind.conf that controls this behavior.

Note that disabling lingering will break tools like screen and tmux used
inside the session. See the man pages for loginctl and logind.conf for
more details.

In your case you have other processes not started by systemd, for example user applications. But the general principle is the same - unfortunately this it is up to the desktop environment to clean up after itself.

You may be able to improve the situation by disabling any uneccesary services which leave behind residual processes, for example gnome-online-accounts(assuming this is not being used).

Hope this helps.

1 Like