{ "content": [ { "type": "text", "text": "# logind.conf.d (man)\n\n## NAME\n\nlogind.conf, logind.conf.d - Login manager configuration files\n\n## SYNOPSIS\n\n/etc/systemd/logind.conf\n/etc/systemd/logind.conf.d/*.conf\n/run/systemd/logind.conf.d/*.conf\n/usr/lib/systemd/logind.conf.d/*.conf\n\n## DESCRIPTION\n\nThese files configure various parameters of the systemd login manager, systemd-\nlogind.service(8). See systemd.syntax(7) for a general description of the syntax.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **CONFIGURATION DIRECTORIES AND PRECEDENCE**\n- **OPTIONS**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "logind.conf.d", "section": "", "mode": "man", "summary": "logind.conf, logind.conf.d - Login manager configuration files", "synopsis": "/etc/systemd/logind.conf\n/etc/systemd/logind.conf.d/*.conf\n/run/systemd/logind.conf.d/*.conf\n/usr/lib/systemd/logind.conf.d/*.conf", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [ { "name": "systemd", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/systemd/1/json" }, { "name": "systemd-logind.service", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/systemd-logind.service/8/json" }, { "name": "loginctl", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/loginctl/1/json" }, { "name": "systemd-system.conf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/systemd-system.conf/5/json" }, { "name": "LOGIND.CONF", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/LOGIND.CONF/5/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 8, "subsections": [] }, { "name": "DESCRIPTION", "lines": 3, "subsections": [] }, { "name": "CONFIGURATION DIRECTORIES AND PRECEDENCE", "lines": 27, "subsections": [] }, { "name": "OPTIONS", "lines": 161, "subsections": [] }, { "name": "SEE ALSO", "lines": 5, "subsections": [] } ], "sections": { "NAME": { "content": "logind.conf, logind.conf.d - Login manager configuration files\n", "subsections": [] }, "SYNOPSIS": { "content": "/etc/systemd/logind.conf\n\n/etc/systemd/logind.conf.d/*.conf\n\n/run/systemd/logind.conf.d/*.conf\n\n/usr/lib/systemd/logind.conf.d/*.conf\n", "subsections": [] }, "DESCRIPTION": { "content": "These files configure various parameters of the systemd login manager, systemd-\nlogind.service(8). See systemd.syntax(7) for a general description of the syntax.\n", "subsections": [] }, "CONFIGURATION DIRECTORIES AND PRECEDENCE": { "content": "The default configuration is set during compilation, so configuration is only needed when it\nis necessary to deviate from those defaults. Initially, the main configuration file in\n/etc/systemd/ contains commented out entries showing the defaults as a guide to the\nadministrator. Local overrides can be created by editing this file or by creating drop-ins,\nas described below. Using drop-ins for local configuration is recommended over modifications\nto the main configuration file.\n\nIn addition to the \"main\" configuration file, drop-in configuration snippets are read from\n/usr/lib/systemd/*.conf.d/, /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/.\nThose drop-ins have higher precedence and override the main configuration file. Files in the\n*.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order,\nregardless of in which of the subdirectories they reside. When multiple files specify the\nsame option, for options which accept just a single value, the entry in the file sorted last\ntakes precedence, and for options which accept a list of values, entries are collected as\nthey occur in the sorted files.\n\nWhen packages need to customize the configuration, they can install drop-ins under /usr/.\nFiles in /etc/ are reserved for the local administrator, who may use this logic to override\nthe configuration files installed by vendor packages. Drop-ins have to be used to override\npackage drop-ins, since the main configuration file has lower precedence. It is recommended\nto prefix all filenames in those subdirectories with a two-digit number and a dash, to\nsimplify the ordering of the files.\n\nTo disable a configuration file supplied by the vendor, the recommended way is to place a\nsymlink to /dev/null in the configuration directory in /etc/, with the same filename as the\nvendor configuration file.\n", "subsections": [] }, "OPTIONS": { "content": "All options are configured in the [Login] section:\n\nNAutoVTs=\nTakes a positive integer. Configures how many virtual terminals (VTs) to allocate by\ndefault that, when switched to and are previously unused, \"autovt\" services are\nautomatically spawned on. These services are instantiated from the template unit\nautovt@.service for the respective VT TTY name, for example, autovt@tty4.service. By\ndefault, autovt@.service is linked to getty@.service. In other words, login prompts are\nstarted dynamically as the user switches to unused virtual terminals. Hence, this\nparameter controls how many login \"gettys\" are available on the VTs. If a VT is already\nused by some other subsystem (for example, a graphical login), this kind of activation\nwill not be attempted. Note that the VT configured in ReserveVT= is always subject to\nthis kind of activation, even if it is not one of the VTs configured with the NAutoVTs=\ndirective. Defaults to 6. When set to 0, automatic spawning of \"autovt\" services is\ndisabled.\n\nReserveVT=\nTakes a positive integer. Identifies one virtual terminal that shall unconditionally be\nreserved for autovt@.service activation (see above). The VT selected with this option\nwill be marked busy unconditionally, so that no other subsystem will allocate it. This\nfunctionality is useful to ensure that, regardless of how many VTs are allocated by other\nsubsystems, one login \"getty\" is always available. Defaults to 6 (in other words, there\nwill always be a \"getty\" available on Alt-F6.). When set to 0, VT reservation is\ndisabled.\n\nKillUserProcesses=\nTakes a boolean argument. Configures whether the processes of a user should be killed\nwhen the user logs out. If true, the scope unit corresponding to the session and all\nprocesses inside that scope will be terminated. If false, the scope is \"abandoned\", see\nsystemd.scope(5), and processes are not killed. Defaults to \"no\", but see the options\nKillOnlyUsers= and KillExcludeUsers= below.\n\nIn addition to session processes, user process may run under the user manager unit\nuser@.service. Depending on the linger settings, this may allow users to run processes\nindependent of their login sessions. See the description of enable-linger in loginctl(1).\n\nNote that setting KillUserProcesses=yes will break tools like screen(1) and tmux(1),\nunless they are moved out of the session scope. See example in systemd-run(1).\n\nKillOnlyUsers=, KillExcludeUsers=\nThese settings take space-separated lists of usernames that override the\nKillUserProcesses= setting. A user name may be added to KillExcludeUsers= to exclude the\nprocesses in the session scopes of that user from being killed even if\nKillUserProcesses=yes is set. If KillExcludeUsers= is not set, the \"root\" user is\nexcluded by default. KillExcludeUsers= may be set to an empty value to override this\ndefault. If a user is not excluded, KillOnlyUsers= is checked next. If this setting is\nspecified, only the processes in the session scopes of those users will be killed.\nOtherwise, users are subject to the KillUserProcesses=yes setting.\n\nIdleAction=\nConfigures the action to take when the system is idle. Takes one of \"ignore\", \"poweroff\",\n\"reboot\", \"halt\", \"kexec\", \"suspend\", \"hibernate\", \"hybrid-sleep\",\n\"suspend-then-hibernate\", and \"lock\". Defaults to \"ignore\".\n\nNote that this requires that user sessions correctly report the idle status to the\nsystem. The system will execute the action after all sessions report that they are idle,\nno idle inhibitor lock is active, and subsequently, the time configured with\nIdleActionSec= (see below) has expired.\n\nIdleActionSec=\nConfigures the delay after which the action configured in IdleAction= (see above) is\ntaken after the system is idle.\n\nInhibitDelayMaxSec=\nSpecifies the maximum time a system shutdown or sleep request is delayed due to an\ninhibitor lock of type \"delay\" being active before the inhibitor is ignored and the\noperation executes anyway. Defaults to 5.\n\nUserStopDelaySec=\nSpecifies how long to keep the user record and per-user service user@.service around for\na user after they logged out fully. If set to zero, the per-user service is terminated\nimmediately when the last session of the user has ended. If this option is configured to\nnon-zero rapid logout/login cycles are sped up, as the user's service manager is not\nconstantly restarted. If set to \"infinity\" the per-user service for a user is never\nterminated again after first login, and continues to run until system shutdown. Defaults\nto 10s.\n\nHandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=, HandleLidSwitch=,\nHandleLidSwitchExternalPower=, HandleLidSwitchDocked=, HandleRebootKey=\nControls how logind shall handle the system power, reboot and sleep keys and the lid\nswitch to trigger actions such as system power-off, reboot or suspend. Can be one of\n\"ignore\", \"poweroff\", \"reboot\", \"halt\", \"kexec\", \"suspend\", \"hibernate\", \"hybrid-sleep\",\n\"suspend-then-hibernate\", and \"lock\". If \"ignore\", logind will never handle these keys.\nIf \"lock\", all running sessions will be screen-locked; otherwise, the specified action\nwill be taken in the respective event. Only input devices with the \"power-switch\" udev\ntag will be watched for key/lid switch events. HandlePowerKey= defaults to \"poweroff\",\nHandleRebootKey= defaults to \"reboot\". HandleSuspendKey= and HandleLidSwitch= default to\n\"suspend\". HandleLidSwitchExternalPower= is completely ignored by default (for backwards\ncompatibility) — an explicit value must be set before it will be used to determine\nbehaviour. HandleLidSwitchDocked= defaults to \"ignore\". HandleHibernateKey= defaults to\n\"hibernate\". If the system is inserted in a docking station, or if more than one display\nis connected, the action specified by HandleLidSwitchDocked= occurs; if the system is on\nexternal power the action (if any) specified by HandleLidSwitchExternalPower= occurs;\notherwise the HandleLidSwitch= action occurs.\n\nA different application may disable logind's handling of system power and sleep keys and\nthe lid switch by taking a low-level inhibitor lock (\"handle-power-key\",\n\"handle-suspend-key\", \"handle-hibernate-key\", \"handle-lid-switch\",\n\"handle-reboot-switch\"). This is most commonly used by graphical desktop environments to\ntake over suspend and hibernation handling, and to use their own configuration\nmechanisms. If a low-level inhibitor lock is taken, logind will not take any action when\nthat key or switch is triggered and the Handle*= settings are irrelevant.\n\nPowerKeyIgnoreInhibited=, SuspendKeyIgnoreInhibited=, HibernateKeyIgnoreInhibited=,\nLidSwitchIgnoreInhibited=, RebootKeyIgnoreInhibited=\nControls whether actions that systemd-logind takes when the power, reboot and sleep keys\nand the lid switch are triggered are subject to high-level inhibitor locks (\"shutdown\",\n\"reboot\", \"sleep\", \"idle\"). Low level inhibitor locks (\"handle-power-key\",\n\"handle-suspend-key\", \"handle-hibernate-key\", \"handle-lid-switch\", \"handle-reboot-key\"),\nare always honored, irrespective of this setting.\n\nThese settings take boolean arguments. If \"no\", the inhibitor locks taken by applications\nare respected. If \"yes\", \"shutdown\", \"reboot\" \"sleep\", and \"idle\" inhibitor locks are\nignored. PowerKeyIgnoreInhibited=, SuspendKeyIgnoreInhibited=,\nHibernateKeyIgnoreInhibited= and RebootKeyIgnoreInhibited= default to \"no\".\nLidSwitchIgnoreInhibited= defaults to \"yes\". This means that when systemd-logind is\nhandling events by itself (no low level inhibitor locks are taken by another\napplication), the lid switch does not respect suspend blockers by default, but the power\nand sleep keys do.\n\nHoldoffTimeoutSec=\nSpecifies a period of time after system startup or system resume in which systemd will\nhold off on reacting to lid events. This is required for the system to properly detect\nany hotplugged devices so systemd can ignore lid events if external monitors, or docks,\nare connected. If set to 0, systemd will always react immediately, possibly before the\nkernel fully probed all hotplugged devices. This is safe, as long as you do not care for\nsystemd to account for devices that have been plugged or unplugged while the system was\noff. Defaults to 30s.\n\nRuntimeDirectorySize=\nSets the size limit on the $XDGRUNTIMEDIR runtime directory for each user who logs in.\nTakes a size in bytes, optionally suffixed with the usual K, G, M, and T suffixes, to the\nbase 1024 (IEC). Alternatively, a numerical percentage suffixed by \"%\" may be specified,\nwhich sets the size limit relative to the amount of physical RAM. Defaults to 10%. Note\nthat this size is a safety limit only. As each runtime directory is a tmpfs file system,\nit will only consume as much memory as is needed.\n\nRuntimeDirectoryInodesMax=\nSets the limit on number of inodes for the $XDGRUNTIMEDIR runtime directory for each\nuser who logs in. Takes a number, optionally suffixed with the usual K, G, M, and T\nsuffixes, to the base 1024 (IEC). Defaults to RuntimeDirectorySize= divided by 4096. Note\nthat this size is a safety limit only. As each runtime directory is a tmpfs file system,\nit will only consume as much memory as is needed.\n\nInhibitorsMax=\nControls the maximum number of concurrent inhibitors to permit. Defaults to 8192 (8K).\n\nSessionsMax=\nControls the maximum number of concurrent user sessions to manage. Defaults to 8192 (8K).\nDepending on how the pamsystemd.so module is included in the PAM stack configuration,\nfurther login sessions will either be refused, or permitted but not tracked by\nsystemd-logind.\n\nRemoveIPC=\nControls whether System V and POSIX IPC objects belonging to the user shall be removed\nwhen the user fully logs out. Takes a boolean argument. If enabled, the user may not\nconsume IPC resources after the last of the user's sessions terminated. This covers\nSystem V semaphores, shared memory and message queues, as well as POSIX shared memory and\nmessage queues. Note that IPC objects of the root user and other system users are\nexcluded from the effect of this setting. Defaults to \"yes\".\n", "subsections": [] }, "SEE ALSO": { "content": "systemd(1), systemd-logind.service(8), loginctl(1), systemd-system.conf(5)\n\n\n\nsystemd 249 LOGIND.CONF(5)", "subsections": [] } } } }