Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Sysadmins got more important things to worry about than 2 processes using barely any resources Commented Jul 2, 2021 at 10:21
  • Related: What does pam_systemd.so do? Commented Jul 2, 2021 at 12:54
  • @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! Commented Jul 3, 2021 at 0:12
  • 1
    @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. Commented Jul 3, 2021 at 0:38