logind.conf, logind.conf.d — Login manager configuration files
These files configure various parameters of the systemd login manager, systemd-logind.service(8).
Configuration files are read from directories in
/usr/lib/, in order of precedence.
Each configuration file in these configuration directories shall be named in
the style of
/etc/ override files with the same name in
/usr/lib/. Files in
/run/ override files with the same name in
Packages should install their configuration files in
/usr/lib/. Files in
reserved for the local administrator, who may use this logic to override the
configuration files installed by vendor packages. All configuration files
are sorted by their filename in lexicographic order, regardless of which of
the directories they reside in. If multiple files specify the same option,
the entry in the file with the lexicographically latest name will take
precedence. It is recommended to prefix all filenames with a two-digit number
and a dash, to simplify the ordering of the files.
If the administrator wants to disable a configuration file supplied by
the vendor, the recommended way is to place a symlink to
/dev/null in the configuration directory in
/etc/, with the same filename as the vendor
Configuration is also read from a single configuration file in
/etc/. This file is read before any of the
configuration directories, and has the lowest precedence; entries in a file
in any configuration directory override entries in the single configuration
All options are configured in the
Takes a positive integer. Configures how many
virtual terminals (VTs) to allocate by default that, when
switched to and are previously unused,
autovt" services are automatically spawned
on. These services are instantiated from the template unit
autovt@.service for the respective VT TTY
name, for example,
autovt@.service is linked to
getty@.service. In other words, login
prompts are started dynamically as the user switches to unused
virtual terminals. Hence, this parameter controls how many
gettys" are available on the VTs. If a
VT is already used by some other subsystem (for example, a
graphical login), this kind of activation will not be
attempted. Note that the VT configured in
ReserveVT= is always subject to this kind
of activation, even if it is not one of the VTs configured
NAutoVTs= directive. Defaults to
6. When set to 0, automatic spawning of
autovt" services is
Takes a positive integer. Identifies one
virtual terminal that shall unconditionally be reserved for
autovt@.service activation (see above).
The VT selected with this option will be marked busy
unconditionally, so that no other subsystem will allocate it.
This functionality is useful to ensure that, regardless of how
many VTs are allocated by other subsystems, one login
getty" is always available. Defaults to 6
(in other words, there will always be a
getty" available on Alt-F6.). When set to 0,
VT reservation is disabled.
Takes a boolean argument. Configures whether
the processes of a user should be killed when the user
completely logs out (i.e. after the user's last session
ended). Defaults to "
Note that setting
will break tools like
These settings take space-separated lists of
usernames that influence the effect of
KillUserProcesses=. If not empty, only
processes of users listed in
will be killed when they log out entirely. Processes of users
KillExcludeUsers= are excluded
from being killed.
defaults to "
root" and takes precedence over
KillOnlyUsers=, which defaults to the empty
Configures the action to take when the system
is idle. Takes one of
Defaults to "
Note that this requires that user sessions correctly
report the idle status to the system. The system will execute
the action after all sessions report that they are idle, no
idle inhibitor lock is active, and subsequently, the time
IdleActionSec= (see below)
Configures the delay after which the action
IdleAction= (see above) is
taken after the system is idle.
Specifies the maximum time a system shutdown
or sleep request is delayed due to an inhibitor lock of type
delay" being active before the inhibitor is
ignored and the operation executes anyway. Defaults to
Controls whether logind shall handle the
system power and sleep keys and the lid switch to trigger
actions such as system power-off or suspend. Can be one of
ignore", logind will never handle these
keys. If "
lock", all running sessions will be
screen-locked; otherwise, the specified action will be taken
in the respective event. Only input devices with the
power-switch" udev tag will be watched for
key/lid switch events.
defaults to "
HandleLidSwitch= default to
HandleLidSwitchDocked= defaults to
HandleHibernateKey= defaults to
hibernate". If the system is inserted in a
docking station, or if more than one display is connected, the
action specified by
occurs; otherwise the
Controls whether actions triggered by the
power and sleep keys and the lid switch are subject to
inhibitor locks. These settings take boolean arguments. If
no", the inhibitor locks taken by
applications in order to block the requested operation are
respected. If "
yes", the requested operation
is executed in any case.
HibernateKeyIgnoreInhibited= default to
LidSwitchIgnoreInhibited= defaults to
yes". This means that the lid switch does
not respect suspend blockers by default, but the power and
sleep keys do.
Sets the size limit on the
$XDG_RUNTIME_DIR runtime directory for each
user who logs in. Takes a size in bytes, optionally suffixed
with the usual K, G, M, and T suffixes, to the base 1024
(IEC). Alternatively, a numerical percentage suffixed by
%" may be specified, which sets the size
limit relative to the amount of physical RAM. Defaults to 10%.
Note that this size is a safety limit only. As each runtime
directory is a tmpfs file system, it will only consume as much
memory as is needed.
Controls whether System V and POSIX IPC
objects belonging to the user shall be removed when the user
fully logs out. Takes a boolean argument. If enabled, the user
may not consume IPC resources after the last of the user's
sessions terminated. This covers System V semaphores, shared
memory and message queues, as well as POSIX shared memory and
message queues. Note that IPC objects of the root user are
excluded from the effect of this setting. Defaults to