1LOGIND.CONF(5) logind.conf LOGIND.CONF(5)
2
3
4
6 logind.conf, logind.conf.d - Login manager configuration files
7
9 /etc/systemd/logind.conf
10
11 /etc/systemd/logind.conf.d/*.conf
12
13 /run/systemd/logind.conf.d/*.conf
14
15 /usr/lib/systemd/logind.conf.d/*.conf
16
18 These files configure various parameters of the systemd login manager,
19 systemd-logind.service(8).
20
22 Default configuration is defined during compilation, so a configuration
23 file is only needed when it is necessary to deviate from those
24 defaults. By default the configuration file in /etc/systemd/ contains
25 commented out entries showing the defaults as a guide to the
26 administrator. This file can be edited to create local overrides.
27
28 When packages need to customize the configuration, they can install
29 configuration snippets in /usr/lib/systemd/*.conf.d/. Files in /etc/
30 are reserved for the local administrator, who may use this logic to
31 override the configuration files installed by vendor packages. The main
32 configuration file is read before any of the configuration directories,
33 and has the lowest precedence; entries in a file in any configuration
34 directory override entries in the single configuration file. Files in
35 the *.conf.d/ configuration subdirectories are sorted by their filename
36 in lexicographic order, regardless of which of the subdirectories they
37 reside in. If multiple files specify the same option, the entry in the
38 file with the lexicographically latest name takes precedence. It is
39 recommended to prefix all filenames in those subdirectories with a
40 two-digit number and a dash, to simplify the ordering of the files.
41
42 To disable a configuration file supplied by the vendor, the recommended
43 way is to place a symlink to /dev/null in the configuration directory
44 in /etc/, with the same filename as the vendor configuration file.
45
47 All options are configured in the "[Login]" section:
48
49 NAutoVTs=
50 Takes a positive integer. Configures how many virtual terminals
51 (VTs) to allocate by default that, when switched to and are
52 previously unused, "autovt" services are automatically spawned on.
53 These services are instantiated from the template unit
54 autovt@.service for the respective VT TTY name, for example,
55 autovt@tty4.service. By default, autovt@.service is linked to
56 getty@.service. In other words, login prompts are started
57 dynamically as the user switches to unused virtual terminals.
58 Hence, this parameter controls how many login "gettys" are
59 available on the VTs. If a VT is already used by some other
60 subsystem (for example, a graphical login), this kind of activation
61 will not be attempted. Note that the VT configured in ReserveVT= is
62 always subject to this kind of activation, even if it is not one of
63 the VTs configured with the NAutoVTs= directive. Defaults to 6.
64 When set to 0, automatic spawning of "autovt" services is disabled.
65
66 ReserveVT=
67 Takes a positive integer. Identifies one virtual terminal that
68 shall unconditionally be reserved for autovt@.service activation
69 (see above). The VT selected with this option will be marked busy
70 unconditionally, so that no other subsystem will allocate it. This
71 functionality is useful to ensure that, regardless of how many VTs
72 are allocated by other subsystems, one login "getty" is always
73 available. Defaults to 6 (in other words, there will always be a
74 "getty" available on Alt-F6.). When set to 0, VT reservation is
75 disabled.
76
77 KillUserProcesses=
78 Takes a boolean argument. Configures whether the processes of a
79 user should be killed when the user completely logs out (i.e. after
80 the user's last session ended). Defaults to "no".
81
82 Note that setting KillUserProcesses=1 will break tools like
83 screen(1).
84
85 KillOnlyUsers=, KillExcludeUsers=
86 These settings take space-separated lists of usernames that
87 influence the effect of KillUserProcesses=. If not empty, only
88 processes of users listed in KillOnlyUsers= will be killed when
89 they log out entirely. Processes of users listed in
90 KillExcludeUsers= are excluded from being killed.
91 KillExcludeUsers= defaults to "root" and takes precedence over
92 KillOnlyUsers=, which defaults to the empty list.
93
94 IdleAction=
95 Configures the action to take when the system is idle. Takes one of
96 "ignore", "poweroff", "reboot", "halt", "kexec", "suspend",
97 "hibernate", "hybrid-sleep", and "lock". Defaults to "ignore".
98
99 Note that this requires that user sessions correctly report the
100 idle status to the system. The system will execute the action after
101 all sessions report that they are idle, no idle inhibitor lock is
102 active, and subsequently, the time configured with IdleActionSec=
103 (see below) has expired.
104
105 IdleActionSec=
106 Configures the delay after which the action configured in
107 IdleAction= (see above) is taken after the system is idle.
108
109 InhibitDelayMaxSec=
110 Specifies the maximum time a system shutdown or sleep request is
111 delayed due to an inhibitor lock of type "delay" being active
112 before the inhibitor is ignored and the operation executes anyway.
113 Defaults to 5.
114
115 HandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=,
116 HandleLidSwitch=, HandleLidSwitchDocked=
117 Controls whether logind shall handle the system power and sleep
118 keys and the lid switch to trigger actions such as system power-off
119 or suspend. Can be one of "ignore", "poweroff", "reboot", "halt",
120 "kexec", "suspend", "hibernate", "hybrid-sleep", and "lock". If
121 "ignore", logind will never handle these keys. If "lock", all
122 running sessions will be screen-locked; otherwise, the specified
123 action will be taken in the respective event. Only input devices
124 with the "power-switch" udev tag will be watched for key/lid switch
125 events. HandlePowerKey= defaults to "poweroff". HandleSuspendKey=
126 and HandleLidSwitch= default to "suspend". HandleLidSwitchDocked=
127 defaults to "ignore". HandleHibernateKey= defaults to "hibernate".
128 If the system is inserted in a docking station, or if more than one
129 display is connected, the action specified by
130 HandleLidSwitchDocked= occurs; otherwise the HandleLidSwitch=
131 action occurs.
132
133 PowerKeyIgnoreInhibited=, SuspendKeyIgnoreInhibited=,
134 HibernateKeyIgnoreInhibited=, LidSwitchIgnoreInhibited=
135 Controls whether actions triggered by the power and sleep keys and
136 the lid switch are subject to inhibitor locks. These settings take
137 boolean arguments. If "no", the inhibitor locks taken by
138 applications in order to block the requested operation are
139 respected. If "yes", the requested operation is executed in any
140 case. PowerKeyIgnoreInhibited=, SuspendKeyIgnoreInhibited= and
141 HibernateKeyIgnoreInhibited= default to "no".
142 LidSwitchIgnoreInhibited= defaults to "yes". This means that the
143 lid switch does not respect suspend blockers by default, but the
144 power and sleep keys do.
145
146 RuntimeDirectorySize=
147 Sets the size limit on the $XDG_RUNTIME_DIR runtime directory for
148 each user who logs in. Takes a size in bytes, optionally suffixed
149 with the usual K, G, M, and T suffixes, to the base 1024 (IEC).
150 Alternatively, a numerical percentage suffixed by "%" may be
151 specified, which sets the size limit relative to the amount of
152 physical RAM. Defaults to 10%. Note that this size is a safety
153 limit only. As each runtime directory is a tmpfs file system, it
154 will only consume as much memory as is needed.
155
156 UserTasksMax=
157 Sets the maximum number of OS tasks each user may run concurrently.
158 This controls the TasksMax= setting of the per-user slice unit, see
159 systemd.resource-control(5) for details.
160
161 RemoveIPC=
162 Controls whether System V and POSIX IPC objects belonging to the
163 user shall be removed when the user fully logs out. Takes a boolean
164 argument. If enabled, the user may not consume IPC resources after
165 the last of the user's sessions terminated. This covers System V
166 semaphores, shared memory and message queues, as well as POSIX
167 shared memory and message queues. Note that IPC objects of the root
168 user are excluded from the effect of this setting. Defaults to
169 "no".
170
172 systemd(1), systemd-logind.service(8), loginctl(1), systemd-
173 system.conf(5)
174
175
176
177systemd 219 LOGIND.CONF(5)