Bug#867710: systemd don't stop user processes reliable on logout, even with KillUserProcesses=yes

Michael Biebl biebl at debian.org
Sun Jul 9 14:50:51 BST 2017


Am 09.07.2017 um 12:05 schrieb Alf Gaida:
> ok - maybe more clear:
> * have a session running
> * have some applications and user processes open
> * end the session
> * when logged out, check running processes
> * be not happy about finding some processes that run with the logged out
> user as owner
>   even if KillUserProcesses=Yes is set.
> 
> And the worst case is if a application appear on your login screen,
> running on the logged out user  - in this case firefox or not so often
> audacious. Will try to make a real photo of it next time it happends.
> 
> I have seen this behaviour some times ago, it stopped with setting
> KillUserProcesses=Yes. But now this behaviour is back and i'm not so
> lucky about. As discussed in the list it is intended that
> KillUserProcesses=Yes really kills all user processes when a user end
> his session. Hope it is now more clear.

Which processes are not killed on logout? The output of system-cgls
might be helpful.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- 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/20170709/e34c679c/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list