4 ms·

When I see “manages user sessions,” I don’t know what that phrase means. What is a “session” (again assuming not a POSIX session leader) and what are we concret

When I see “manages user sessions,” I don’t know what that phrase means. What is a “session” (again assuming not a POSIX session leader) and what are we concretely doing to “manage” it? Is there a guide that explains the bare minimum that typical end users need to know to stop systemd from breaking use cases that have worked for years? I would never expect a non-sysadmin to have read the “systemd-run” or “loginctl” manpages or know how to find them. I’m a nerd and even I don’t know how to get to the point of understanding what https://man7.org/linux/man-pages/man1/systemd-run.1.html https://man7.org/linux/man-pages/man1/systemd-run.1.html is trying to tell me.

teddyh 4y ago
I mentioned systemd-logind. Its manual page systemd-logind(8) states¹: “See sd-login(3)² for information about the basic concepts of logind such as users, sessions and seats.”. 1. https://manpages.debian.org/stable/systemd/systemd-logind.8.en.html https://manpages.debian.org/stable/systemd/systemd-logind.8.... 2. https://manpages.debian.org/bullseye/libsystemd-dev/sd-login.3.en.html https://manpages.debian.org/bullseye/libsystemd-dev/sd-login...
effie 4y ago
> the bare minimum that typical end users need to know to stop systemd from breaking use cases that have worked for years? That is bound to be a losing strategy. Systemd development (of breaking changes) is not stopping anytime soon. The simplest solution is to switch to an OS without systemd, like Devuan or Alpine or BSD.