1SYSTEMD-LOGIND.SERVICE(8)   systemd-logind.service   SYSTEMD-LOGIND.SERVICE(8)
2
3
4

NAME

6       systemd-logind.service, systemd-logind - Login manager
7

SYNOPSIS

9       systemd-logind.service
10
11       /usr/lib/systemd/systemd-logind
12

DESCRIPTION

14       systemd-logind is a system service that manages user logins. It is
15       responsible for:
16
17       •   Keeping track of users and sessions, their processes and their idle
18           state. This is implemented by allocating a systemd slice unit for
19           each user below user.slice, and a scope unit below it for each
20           concurrent session of a user. Also, a per-user service manager is
21           started as system service instance of user@.service for each logged
22           in user.
23
24       •   Generating and managing session IDs. If auditing is available and
25           an audit session ID is already set for a session, then this ID is
26           reused as the session ID. Otherwise, an independent session counter
27           is used.
28
29       •   Providing polkit[1]-based access for users for operations such as
30           system shutdown or sleep
31
32       •   Implementing a shutdown/sleep inhibition logic for applications
33
34       •   Handling of power/sleep hardware keys
35
36       •   Multi-seat management
37
38       •   Session switch management
39
40       •   Device access management for users
41
42       •   Automatic spawning of text logins (gettys) on virtual console
43           activation and user runtime directory management
44
45       User sessions are registered with logind via the pam_systemd(8) PAM
46       module.
47
48       See logind.conf(5) for information about the configuration of this
49       service.
50
51       See sd-login(3) for information about the basic concepts of logind such
52       as users, sessions and seats.
53
54       See org.freedesktop.login1(5) and org.freedesktop.LogControl1(5) for
55       information about the D-Bus APIs systemd-logind provides.
56
57       For more information on the inhibition logic see the Inhibitor Lock
58       Developer Documentation[2].
59
60       If you are interested in writing a display manager that makes use of
61       logind, please have look at Writing Display Managers[3]. If you are
62       interested in writing a desktop environment that makes use of logind,
63       please have look at Writing Desktop Environments[4].
64

SEE ALSO

66       systemd(1), systemd-user-sessions.service(8), loginctl(1),
67       logind.conf(5), pam_systemd(8), sd-login(3)
68

NOTES

70        1. polkit
71           http://www.freedesktop.org/wiki/Software/polkit
72
73        2. Inhibitor Lock Developer Documentation
74           https://www.freedesktop.org/wiki/Software/systemd/inhibit
75
76        3. Writing Display Managers
77           https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers
78
79        4. Writing Desktop Environments
80           http://www.freedesktop.org/wiki/Software/systemd/writing-desktop-environments
81
82
83
84systemd 248                                          SYSTEMD-LOGIND.SERVICE(8)
Impressum