Re: systemd-logind on Linux servers - to be or not to be?

From	Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups	comp.os.linux.misc
Subject	Re: systemd-logind on Linux servers - to be or not to be?
Date	2024-11-01 20:40 +0000
Organization	A noiseless patient Spider
Message-ID	<vg3eb3$3d77d$1@dont-email.me> (permalink)
References	<b88fvk-1u6.ln1@intheattic.eternal-september.org>

Show all headers | View raw

On Fri, 1 Nov 2024 16:21:15 +0100, Juancho wrote:

> The only practical difference I can see is that the command "loginctl
> session-status" works in that Ubuntu Server 22.04 install, but does not
> work ("Failed to connect to bus: No such file or directory") in that
> Debian 12 install. Other than that, both systems run the same to my
> eyes.

Debian certainly has the option to run systemd-logind. For example,
loginctl does work and print useful results on my Debian Unstable
setup.

> Therefore, my question for more experienced Linux gurus, is this: Does
> systemd-logind provide any value in a Linux server setup?

As is usual with systemd, it tends to provide functionality in places
where other alternatives don’t even have places.

<https://www.freedesktop.org/software/systemd/man/latest/systemd-logind.html>
<https://www.freedesktop.org/software/systemd/man/latest/logind.conf.html>

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Find similar

Thread

systemd-logind on Linux servers - to be or not to be? Juancho <eternal@notreally.com> - 2024-11-01 16:21 +0100
  Re: systemd-logind on Linux servers - to be or not to be? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-01 20:40 +0000

csiph-web