logind.conf
elogind
Developer
Lennart
Poettering
lennart@poettering.net
logind.conf
5
logind.conf
Login manager configuration files
/etc/elogind/logind.conf
Description
These files configure various parameters of the elogind
login manager.
Options
All login options are configured in the
[Login] section, system sleep options are
configured in the [Sleep] section.
[Login] section:
KillUserProcesses=
Takes a boolean argument. Configures whether the processes of a
user should be killed when the user logs out. If true, the processes
listed in their session cgroup will be terminated. If false, the session cgroup
is ignored
and processes are not killed. Defaults to yes,
but see the options KillOnlyUsers= and
KillExcludeUsers= below.
Note that setting KillUserProcesses=yes
will break tools like
screen1
and
tmux1,
unless they are moved out of the session scope.
KillOnlyUsers=
KillExcludeUsers=
These settings take space-separated lists of usernames that override
the KillUserProcesses= setting. A user name may be added to
KillExcludeUsers= to exclude the processes in the session scopes of
that user from being killed even if KillUserProcesses=yes is set. If
KillExcludeUsers= is not set, the root user is
excluded by default. KillExcludeUsers= may be set to an empty value
to override this default. If a user is not excluded, KillOnlyUsers=
is checked next. If this setting is specified, only the session scopes of those users
will be killed. Otherwise, users are subject to the
KillUserProcesses=yes setting.
IdleAction=
Configures the action to take when the system
is idle. Takes one of
ignore,
poweroff,
reboot,
halt,
kexec,
suspend,
hibernate,
hybrid-sleep, and
lock.
Defaults to ignore.
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
configured with IdleActionSec= (see below)
has expired.
IdleActionSec=
Configures the delay after which the action
configured in IdleAction= (see above) is
taken after the system is idle.
InhibitDelayMaxSec=
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
5.
HandlePowerKey=
HandleSuspendKey=
HandleHibernateKey=
HandleLidSwitch=
HandleLidSwitchDocked=
Controls how 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,
poweroff,
reboot,
halt,
kexec,
suspend,
hibernate,
hybrid-sleep, and
lock.
If 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. HandlePowerKey=
defaults to poweroff.
HandleSuspendKey= and
HandleLidSwitch= default to
suspend.
HandleLidSwitchDocked= defaults to
ignore.
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 HandleLidSwitchDocked=
occurs; otherwise the HandleLidSwitch=
action occurs.
A different application may disable logind's handling of system power and
sleep keys and the lid switch by taking a low-level inhibitor lock
(handle-power-key, handle-suspend-key,
handle-hibernate-key, handle-lid-switch).
This is most commonly used by graphical desktop environments
to take over suspend and hibernation handling, and to use their own configuration
mechanisms. If a low-level inhibitor lock is taken, logind will not take any
action when that key or switch is triggered and the Handle*=
settings are irrelevant.
PowerKeyIgnoreInhibited=
SuspendKeyIgnoreInhibited=
HibernateKeyIgnoreInhibited=
LidSwitchIgnoreInhibited=
Controls whether actions that systemd-logind
takes when the power and sleep keys and the lid switch are triggered are subject
to high-level inhibitor locks ("shutdown", "sleep", "idle"). Low level inhibitor
locks (handle-power-key, handle-suspend-key,
handle-hibernate-key, handle-lid-switch),
are always honored, irrespective of this setting.
These settings take boolean arguments. If no, the
inhibitor locks taken by applications are respected. If yes,
"shutdown", "sleep", and "idle" inhibitor locks are ignored.
PowerKeyIgnoreInhibited=,
SuspendKeyIgnoreInhibited=, and
HibernateKeyIgnoreInhibited= default to no.
LidSwitchIgnoreInhibited= defaults to yes.
This means that when systemd-logind is handling events by
itself (no low level inhibitor locks are taken by another application), the lid
switch does not respect suspend blockers by default, but the power and sleep keys
do.
HoldoffTimeoutSec=
Specifies the timeout after system startup or
system resume in which systemd will hold off on reacting to
lid events. This is required for the system to properly
detect any hotplugged devices so systemd can ignore lid events
if external monitors, or docks, are connected. If set to 0,
systemd will always react immediately, possibly before the
kernel fully probed all hotplugged devices. This is safe, as
long as you do not care for systemd to account for devices
that have been plugged or unplugged while the system was off.
Defaults to 30s.
RuntimeDirectorySize=
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.
InhibitorsMax=
Controls the maximum number of concurrent inhibitors to permit. Defaults to 8192
(8K).
SessionsMax=
Controls the maximum number of concurrent user sessions to manage. Defaults to 8192
(8K). Depending on how the pam_systemd.so module is included in the PAM stack
configuration, further login sessions will either be refused, or permitted but not tracked by
systemd-logind.
UserTasksMax=
Sets the maximum number of OS tasks each user may run concurrently. This controls the
TasksMax= setting of the per-user slice unit, see
systemd.resource-control5
for details. If assigned the special value infinity, no tasks limit is applied.
Defaults to 33%, which equals 10813 with the kernel's defaults on the host, but might be smaller in
OS containers.
RemoveIPC=
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 and other system users
are excluded from the effect of this setting. Defaults to yes.
[Sleep] section:
elogind supports three general
power-saving modes:
suspend
a low-power state
where execution of the OS is paused,
and complete power loss might result
in lost data, and which is fast to
enter and exit. This corresponds to
suspend, standby, or freeze states as
understood by the kernel.
hibernate
a low-power state
where execution of the OS is paused,
and complete power loss does not
result in lost data, and which might
be slow to enter and exit. This
corresponds to the hibernation as
understood by the kernel.
hybrid-sleep
a low-power state
where execution of the OS is paused,
which might be slow to enter, and on
complete power loss does not result in
lost data but might be slower to exit
in that case. This mode is called
suspend-to-both by the kernel.
SuspendMode=
HibernateMode=
HybridSleepMode=
The string to be written to
/sys/power/disk by elogind.
More than one value can be specified by separating
multiple values with whitespace. They will be tried
in turn, until one is written without error. If
neither succeeds, the operation will be aborted.
SuspendState=
HibernateState=
HybridSleepState=
The string to be written to
/sys/power/state by elogind.
More than one value can be specified by separating
multiple values with whitespace. They will be tried
in turn, until one is written without error. If
neither succeeds, the operation will be aborted.
See Also
elogind8,
loginctl1,