Timeline for Unwanted desktop processes started by systemd at ssh login
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2022 at 15:08 | answer | added | eMPee584 | timeline score: 1 | |
| Jul 3, 2021 at 0:38 | comment | added | wef | @steeldriver - thanks for the useful link which led me to remove the pam_systemd.so line from /etc/pam.d/system-auth. Now I can log in without the cruft. Next, I need to find out how to prepare such a login for a GUI session - should I want one!! Running 'systemd --user' doesn't do it. | |
| Jul 3, 2021 at 0:12 | comment | added | wef | @Panki - I beg to differ. Imagine (as in my previous employer) 1000's of linux VM instances, dozens of ops staff, possibly hundreds of automated ssh jobs - it adds up. I admit that for me on my home setup, it's just an untidiness; a lack of minimalism. As a Unix greybeard, I hate that and I'm suspicious of what these youngsters are doing with systemd! | |
| Jul 2, 2021 at 12:54 | comment | added | steeldriver | Related: What does pam_systemd.so do? | |
| Jul 2, 2021 at 10:21 | comment | added | Panki | Sysadmins got more important things to worry about than 2 processes using barely any resources | |
| Jul 2, 2021 at 7:16 | history | asked | wef | CC BY-SA 4.0 |