Number of 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
In other words, login prompts are started dynamically as the user switches to unused virtual terminals.
this controls how many login "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.
the VT configured in
ReserveVT is always subject to this kind of activation, even if it is not one of the VTs configured with the NAutoVTs=
directive. Defaults to 6. 0 disables automatic spawning of
Identifies one virtual terminal that shall unconditionally be reserved for
activation, will be marked busy, no other subsystem will allocate it.
Useful to ensure that 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.
If enabled, after the last of the user's sessions terminated
System V semaphores, shared memory and message queues, as well as POSIX shared memory and message queues
IPC objects of
root and other system users(?) are excluded from this . Defaults to "yes".
Limit on |
$XDG_RUNTIME_DIR runtime directory for each user in bytes,
KillExcludeUsers= uname uname …
| Users excluded from having processes killed. If not set root user is excluded, unless set to an empty value.|
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
Should processes of a user be killed when the user logs out.
yes the scope unit corresponding to the session and all processes inside that scope will be terminated.
no the scope is "abandoned", see systemd.scope(5), and processes are not killed.
In addition to session processes, user process may run under the user manager
This allows users to run processes independent of their login sessions. See
enable-linger in loginctl(1).
KillUserProcesses=yes breaks screen(1) and tmux(1), unless they are moved out of the session scope. See example in systemd-run(1).
| when the system is idle: |
ignore, poweroff, reboot, halt, kexec,
suspend, hibernate, hybrid-sleep or
The system will execute the action after all sessions report that they are idle, no idle inhibitor lock is active and
IdleActionSec has expired.
| delay after which |
IdleAction is taken after the system is idle.
maximum time a shutdown or sleep is delayed due to an inhibitor lock of |
handle power, sleep keys and lid switch to trigger actions|
ignore, poweroff, reboot, halt, kexec, suspend, hibernate, hybrid-sleep, or
(all running sessions will be screen-locked)
HandlePowerKey defaults to
poweroff (may be overylayed to shutdown)
HandleLidSwitch default to
HandleLidSwitchDocked defaults to
HandleHibernateKey defaults to
Only input devices with the "power-switch" udev tag will be watched for key/lid switch events.
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.
actions are subject to high-level inhibitor locks (|
shutdown, sleep, idle).
Low level inhibitor locks (
handle-*-key) are always honored
no : inhibitor locks by applications are respected.
idle inhibitor locks are ignored.
PowerKeyIgnoreInhibited, SuspendKeyIgnoreInhibited and
HibernateKeyIgnoreInhibited default to
LidSwitchIgnoreInhibited defaults to
| maximum concurrent inhibitors . Defaults 8192
after startup or resume, delay reacting to lid events
to properly detect hotplugged devices so systemd can ignore lid events if monitors, or docks, are connected.
| maximum number of concurrent user sessions to manage. Defaults to 8192 |
Depending on how
is included in the PAM stack configuration, further login sessions will either be refused, or permitted but not
tracked by systemd-logind.
maximum number of OS tasks each user may run concurrently. controls |
TasksMax of the per-user slice
unit, see systemd.resource-control(5) .
infinity no tasks limit
Defaults 33%, which equals 10813 with the kernel's defaults on the host, but might be smaller in OS containers.