Bug 14781 - 5b1: KillUserProcesses=yes not killing all processes upon log out
Summary: 5b1: KillUserProcesses=yes not killing all processes upon log out
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-12-11 17:58 CET by Bit Twister
Modified: 2015-05-21 11:43 CEST (History)
0 users

See Also:
Source RPM: systemd-217-7.mga5.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2014-12-11 17:58:02 CET
Description of problem:

KillUserProcesses=yes not killing all processes upon log out

$  cat /etc/sysconfig/desktop
DISPLAYMANAGER=kdm
DESKTOP=KDE4

$ grep KillUserProcesses /etc/systemd/logind.conf
KillUserProcesses=yes

$ grep START_GPGAGENT /etc/sysconfig/gnupg2
START_GPGAGENT="no"
START_GPGAGENT_SH="no"

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. change KillUserProcesses=yes in /etc/systemd/logind.conf
2. set run level 3
3. create a test account, say, junk
4. reboot
5. log into your account
6. startx
7. click up a terminal
8. su - junk
9. firefox
10. close firefox
11. exit
12. ps aux | grep junk




Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-12-13 23:51:03 CET

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Samuel Verschelde 2015-05-21 11:39:02 CEST

Whiteboard: (none) => MGA5TOO

Comment 1 Colin Guthrie 2015-05-21 11:43:29 CEST
"su -" does not create a user session so the logind option KillUserProcesses (or any other option) has no effect here.

You cannot create a user session within an exisitng user session (not without complications - this is why startx itself has to inherit the existing user session and thus the type is listed as text rather than graphical and we cannot switch tty or we will lose all ACL permissions etc).

Anyway, what you are doing here is totally expected within the context of logind (i.e. logind is not used at all here).

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.