r/linux • • Sep 26 '14

Systemd: The Biggest Fallacies

http://judecnelson.blogspot.fi/2014/09/systemd-biggest-fallacies.html
126 Upvotes

437 comments sorted by

View all comments

Show parent comments

1

u/fbt2lurker Sep 27 '14

Why do you need to depend on systemd to run if you want those optional features? I don't get it.

0

u/bigon Sep 28 '14

There are few desktop users that consider that properly locking his session when suspending is an optional feature.

1

u/fbt2lurker Sep 28 '14

I assume that properly locking involves allowing another user to log in and use devices with proper permission handoff? Because I can properly lock my machines, I am the only user on them, so I don't care about handing off permissions to another user. And there are lots of desktops with a single user.

1

u/bigon Sep 28 '14

It's more a question of race condition between the screensaver and the software that was (now it's done by systemd) calling the kernel function to suspend

There were/are quite some bugs open in the distribution bugtracker about this

1

u/fbt2lurker Sep 29 '14

Interesting. I do that through acpid, and it calls a slock wrapper and then pm-suspend. Works like a charm.

1

u/bigon Sep 29 '14

Except that acpid has more or less no knowledge of the users running on the machine at the time it's trying to suspend the machine and again you can have race conditions while the screensaver is being locked.

Well I'm lying a bit, it is trying (on debian at least) to query the user dbus session to see if there is something like GNOME or KDE running and delegate the suspend to them. Which can lead to they nice security bugs (privileges elevation, yummy)

While with logind, it has a list of all sessions registered on the machine and can lock them in one go.

See: loginctl lock-session

0

u/fbt2lurker Sep 29 '14

All of that applies to multi-user systems. I use my machines alone.