Description of problem: After logging in and logging out one would expect that processes owned by the id in question would terminate. There is an exception. There are pairs left behind despite that user 'michal' is not logged in at this moment: # pgrep -u michal -a 1911 systemd 1912 (sd-pam) michal 1911 ... Feb20 0:00 /usr/lib/systemd/systemd --user michal 1912 ... Feb20 0:00 \_ (sd-pam) There will be no more of such pairs on the next login of 'michal' but it still does not smell right. Even less so on an installation with a big number of users coming and going. Version-Release number of selected component (if applicable): systemd-208-14.fc20 How reproducible: always Additional info: I wonder if this is not somehow related to an infamous "ssh connection left hanging after poweroff" bug 626477?
Yes, processes are left around because we don't clean up properly. We could, but then we run into bug 1053315. This area is much better with systemd-210..., but the problems with cron are not solved either.
Did you use "loginctl set-linger" on your user maybe?
(In reply to Lennart Poettering from comment #2) > Did you use "loginctl set-linger" on your user maybe? Definitely not. Until you asked I was not even aware that such possibility exists. I guess that you mean 'enable-linger' as 'man loginctl' fails to mention 'set-linger'. In the meantime I looked at other machines running Fedora 20. The reported behaviour is consistent across different installations.
I was just hit by this when I tried to remove a user on my Fedora 20. The reproducer is as simple as: # adduser mgrepl # su - mgrepl $ systemctl --user status default.target > /dev/null $ logout # userdel -r mgrepl userdel: user mgrepl is currently used by process 1538
Hit the same issue. Managed to kill the user by manually stopping the user unit via: $ systemctl stop user@<target-user-id>.service $ userdel -r <target-user> As Simon, I never ran loginctl set-linger. - Gilboa
still observing this after upgrade to f21 systemd-216-12.fc21.i686
This should be fixed upstream now, I'll make a new systemd for F21 this week.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.