systemd-logind.service(8)

•Keeping track of users and sessions, their processes and their idle state. This is implemented by allocating a systemd slice unit for each user below user.slice, and a scope unit below it for each concurrent session of a user. Also, a per-user service manager is started as system service instance of user@.service for each logged in user.

•Generating and managing session IDs. If auditing is available and an audit session ID is already set for a session, then this ID is reused as the session ID. Otherwise, an independent session counter is used.

•Providing polkit[1]-based access for users for operations such as system shutdown or sleep

.RE

.PP User sessions are registered with logind via the pam_systemd(8) PAM module.

.PP See logind.conf(5) for information about the configuration of this service.

.PP See sd-login(3) for information about the basic concepts of logind such as users, sessions and seats.

.PP See org.freedesktop.login1(5) and org.freedesktop.LogControl1(5) for information about the D-Bus APIs systemd-logind provides.

.PP In addition to the D-Bus interface, systemd-logind also provides a Varlink interface io.systemd.Shutdown for shutting down or rebooting the system. It supports PowerOff, Reboot, Halt, KExec, and SoftReboot methods. Each method accepts an optional skipInhibitors boolean parameter to bypass active block inhibitors (matching the SD_LOGIND_SKIP_INHIBITORS flag of the D-Bus interface). The interface can be queried with varlinkctl introspect /run/systemd/io.systemd.Login io.systemd.Shutdown.

.PP For more information see Inhibitor Locks[2].

.PP If you are interested in writing a display manager that makes use of logind, please have look at Writing Display Managers[3]. If you are interested in writing a desktop environment that makes use of logind, please have look at Writing Desktop Environments[4].

.SH "SIGNAL"

.PP SIGHUP