diff options
Diffstat (limited to 'man/logind.conf.d.html')
| -rw-r--r-- | man/logind.conf.d.html | 192 |
1 files changed, 0 insertions, 192 deletions
diff --git a/man/logind.conf.d.html b/man/logind.conf.d.html deleted file mode 100644 index 811411652f..0000000000 --- a/man/logind.conf.d.html +++ /dev/null @@ -1,192 +0,0 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>logind.conf</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><style> - a.headerlink { - color: #c60f0f; - font-size: 0.8em; - padding: 0 4px 0 4px; - text-decoration: none; - visibility: hidden; - } - - a.headerlink:hover { - background-color: #c60f0f; - color: white; - } - - h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink { - visibility: visible; - } - </style><a href="index.html">Index </a>· - <a href="systemd.directives.html">Directives </a>· - <a href="../python-systemd/index.html">Python </a>· - - <span style="float:right">systemd 221</span><hr><div class="refentry"><a name="logind.conf"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>logind.conf, logind.conf.d — Login manager configuration files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">/etc/systemd/logind.conf</code></p><p><code class="filename">/etc/systemd/logind.conf.d/*.conf</code></p><p><code class="filename">/run/systemd/logind.conf.d/*.conf</code></p><p><code class="filename">/usr/lib/systemd/logind.conf.d/*.conf</code></p></div><div class="refsect1"><a name="idm47604601717168"></a><h2 id="Description">Description<a class="headerlink" title="Permalink to this headline" href="#Description">¶</a></h2><p>These files configure various parameters of the systemd - login manager, - <a href="systemd-logind.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-logind.service</span>(8)</span></a>. - </p></div><div class="refsection"><a name="main-conf"></a><h2>Configuration Directories and Precedence</h2><p>Default configuration is defined during compilation, so a - configuration file is only needed when it is necessary to deviate - from those defaults. By default the configuration file in - <code class="filename">/etc/systemd/</code> contains commented out entries - showing the defaults as a guide to the administrator. This file - can be edited to create local overrides. - </p><p>When packages need to customize the configuration, they can - install configuration snippets in - <code class="filename">/usr/lib/systemd/*.conf.d/</code>. Files in - <code class="filename">/etc/</code> are reserved for the local - administrator, who may use this logic to override the - configuration files installed by vendor packages. The main - configuration 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 file. Files in the - <code class="filename">*.conf.d/</code> configuration subdirectories - are sorted by their filename in lexicographic order, regardless of - which of the subdirectories they reside in. If multiple files - specify the same option, the entry in the file with the - lexicographically latest name takes precedence. It is recommended - to prefix all filenames in those subdirectories with a two-digit - number and a dash, to simplify the ordering of the files.</p><p>To disable a configuration file supplied by the vendor, the - recommended way is to place a symlink to - <code class="filename">/dev/null</code> in the configuration directory in - <code class="filename">/etc/</code>, with the same filename as the vendor - configuration file.</p></div><div class="refsect1"><a name="idm47604596812848"></a><h2 id="Options">Options<a class="headerlink" title="Permalink to this headline" href="#Options">¶</a></h2><p>All options are configured in the - "<code class="literal">[Login]</code>" section:</p><div class="variablelist"><dl class="variablelist"><dt id="NAutoVTs="><span class="term"><code class="varname">NAutoVTs=</code></span><a class="headerlink" title="Permalink to this term" href="#NAutoVTs=">¶</a></dt><dd><p>Takes a positive integer. Configures how many - virtual terminals (VTs) to allocate by default that, when - switched to and are previously unused, - "<code class="literal">autovt</code>" services are automatically spawned - on. These services are instantiated from the template unit - <code class="filename">autovt@.service</code> for the respective VT TTY - name, for example, <code class="filename">autovt@tty4.service</code>. - By default, <code class="filename">autovt@.service</code> is linked to - <code class="filename">getty@.service</code>. In other words, login - prompts are started dynamically as the user switches to unused - virtual terminals. Hence, this parameter controls how many - login "<code class="literal">gettys</code>" 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 - <code class="varname">ReserveVT=</code> is always subject to this kind - of activation, even if it is not one of the VTs configured - with the <code class="varname">NAutoVTs=</code> directive. Defaults to - 6. When set to 0, automatic spawning of - "<code class="literal">autovt</code>" services is - disabled.</p></dd><dt id="ReserveVT="><span class="term"><code class="varname">ReserveVT=</code></span><a class="headerlink" title="Permalink to this term" href="#ReserveVT=">¶</a></dt><dd><p>Takes a positive integer. Identifies one - virtual terminal that shall unconditionally be reserved for - <code class="filename">autovt@.service</code> 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 - "<code class="literal">getty</code>" is always available. Defaults to 6 - (in other words, there will always be a - "<code class="literal">getty</code>" available on Alt-F6.). When set to 0, - VT reservation is disabled.</p></dd><dt id="KillUserProcesses="><span class="term"><code class="varname">KillUserProcesses=</code></span><a class="headerlink" title="Permalink to this term" href="#KillUserProcesses=">¶</a></dt><dd><p>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 "<code class="literal">no</code>".</p><p>Note that setting <code class="varname">KillUserProcesses=1</code> - will break tools like - <a href="http://linux.die.net/man/1/screen"><span class="citerefentry"><span class="refentrytitle">screen</span>(1)</span></a>.</p></dd><dt id="KillOnlyUsers="><span class="term"><code class="varname">KillOnlyUsers=</code>, </span><span class="term"><code class="varname">KillExcludeUsers=</code></span><a class="headerlink" title="Permalink to this term" href="#KillOnlyUsers=">¶</a></dt><dd><p>These settings take space-separated lists of - usernames that influence the effect of - <code class="varname">KillUserProcesses=</code>. If not empty, only - processes of users listed in <code class="varname">KillOnlyUsers=</code> - will be killed when they log out entirely. Processes of users - listed in <code class="varname">KillExcludeUsers=</code> are excluded - from being killed. <code class="varname">KillExcludeUsers=</code> - defaults to "<code class="literal">root</code>" and takes precedence over - <code class="varname">KillOnlyUsers=</code>, which defaults to the empty - list.</p></dd><dt id="IdleAction="><span class="term"><code class="varname">IdleAction=</code></span><a class="headerlink" title="Permalink to this term" href="#IdleAction=">¶</a></dt><dd><p>Configures the action to take when the system - is idle. Takes one of - "<code class="literal">ignore</code>", - "<code class="literal">poweroff</code>", - "<code class="literal">reboot</code>", - "<code class="literal">halt</code>", - "<code class="literal">kexec</code>", - "<code class="literal">suspend</code>", - "<code class="literal">hibernate</code>", - "<code class="literal">hybrid-sleep</code>", and - "<code class="literal">lock</code>". - Defaults to "<code class="literal">ignore</code>".</p><p>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 <code class="varname">IdleActionSec=</code> (see below) - has expired.</p></dd><dt id="IdleActionSec="><span class="term"><code class="varname">IdleActionSec=</code></span><a class="headerlink" title="Permalink to this term" href="#IdleActionSec=">¶</a></dt><dd><p>Configures the delay after which the action - configured in <code class="varname">IdleAction=</code> (see above) is - taken after the system is idle.</p></dd><dt id="InhibitDelayMaxSec="><span class="term"><code class="varname">InhibitDelayMaxSec=</code></span><a class="headerlink" title="Permalink to this term" href="#InhibitDelayMaxSec=">¶</a></dt><dd><p>Specifies the maximum time a system shutdown - or sleep request is delayed due to an inhibitor lock of type - "<code class="literal">delay</code>" being active before the inhibitor is - ignored and the operation executes anyway. Defaults to - 5.</p></dd><dt id="HandlePowerKey="><span class="term"><code class="varname">HandlePowerKey=</code>, </span><span class="term"><code class="varname">HandleSuspendKey=</code>, </span><span class="term"><code class="varname">HandleHibernateKey=</code>, </span><span class="term"><code class="varname">HandleLidSwitch=</code>, </span><span class="term"><code class="varname">HandleLidSwitchDocked=</code></span><a class="headerlink" title="Permalink to this term" href="#HandlePowerKey=">¶</a></dt><dd><p>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 - "<code class="literal">ignore</code>", - "<code class="literal">poweroff</code>", - "<code class="literal">reboot</code>", - "<code class="literal">halt</code>", - "<code class="literal">kexec</code>", - "<code class="literal">suspend</code>", - "<code class="literal">hibernate</code>", - "<code class="literal">hybrid-sleep</code>", and - "<code class="literal">lock</code>". - If "<code class="literal">ignore</code>", logind will never handle these - keys. If "<code class="literal">lock</code>", all running sessions will be - screen-locked; otherwise, the specified action will be taken - in the respective event. Only input devices with the - "<code class="literal">power-switch</code>" udev tag will be watched for - key/lid switch events. <code class="varname">HandlePowerKey=</code> - defaults to "<code class="literal">poweroff</code>". - <code class="varname">HandleSuspendKey=</code> and - <code class="varname">HandleLidSwitch=</code> default to - "<code class="literal">suspend</code>". - <code class="varname">HandleLidSwitchDocked=</code> defaults to - "<code class="literal">ignore</code>". - <code class="varname">HandleHibernateKey=</code> defaults to - "<code class="literal">hibernate</code>". If the system is inserted in a - docking station, or if more than one display is connected, the - action specified by <code class="varname">HandleLidSwitchDocked=</code> - occurs; otherwise the <code class="varname">HandleLidSwitch=</code> - action occurs.</p></dd><dt id="PowerKeyIgnoreInhibited="><span class="term"><code class="varname">PowerKeyIgnoreInhibited=</code>, </span><span class="term"><code class="varname">SuspendKeyIgnoreInhibited=</code>, </span><span class="term"><code class="varname">HibernateKeyIgnoreInhibited=</code>, </span><span class="term"><code class="varname">LidSwitchIgnoreInhibited=</code></span><a class="headerlink" title="Permalink to this term" href="#PowerKeyIgnoreInhibited=">¶</a></dt><dd><p>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 - "<code class="literal">no</code>", the inhibitor locks taken by - applications in order to block the requested operation are - respected. If "<code class="literal">yes</code>", the requested operation - is executed in any case. - <code class="varname">PowerKeyIgnoreInhibited=</code>, - <code class="varname">SuspendKeyIgnoreInhibited=</code> and - <code class="varname">HibernateKeyIgnoreInhibited=</code> default to - "<code class="literal">no</code>". - <code class="varname">LidSwitchIgnoreInhibited=</code> defaults to - "<code class="literal">yes</code>". This means that the lid switch does - not respect suspend blockers by default, but the power and - sleep keys do. </p></dd><dt id="HoldoffTimeoutSec="><span class="term"><code class="varname">HoldoffTimeoutSec=</code></span><a class="headerlink" title="Permalink to this term" href="#HoldoffTimeoutSec=">¶</a></dt><dd><p>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.</p></dd><dt id="RuntimeDirectorySize="><span class="term"><code class="varname">RuntimeDirectorySize=</code></span><a class="headerlink" title="Permalink to this term" href="#RuntimeDirectorySize=">¶</a></dt><dd><p>Sets the size limit on the - <code class="varname">$XDG_RUNTIME_DIR</code> 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 - "<code class="literal">%</code>" 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. </p></dd><dt id="RemoveIPC="><span class="term"><code class="varname">RemoveIPC=</code></span><a class="headerlink" title="Permalink to this term" href="#RemoveIPC=">¶</a></dt><dd><p>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 - "<code class="literal">yes</code>".</p></dd></dl></div></div><div class="refsect1"><a name="idm47604596745808"></a><h2 id="See Also">See Also<a class="headerlink" title="Permalink to this headline" href="#See%20Also">¶</a></h2><p> - <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>, - <a href="systemd-logind.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-logind.service</span>(8)</span></a>, - <a href="loginctl.html"><span class="citerefentry"><span class="refentrytitle">loginctl</span>(1)</span></a>, - <a href="systemd-system.conf.html"><span class="citerefentry"><span class="refentrytitle">systemd-system.conf</span>(5)</span></a> - </p></div></div></body></html> |