summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorMichael Biebl <mbiebl@gmail.com>2017-03-31 08:01:41 +0200
committerLennart Poettering <lennart@poettering.net>2017-03-31 08:01:41 +0200
commit3daffa82c421c538f279d7409f868de9311b6c53 (patch)
tree5cca1ede351097a1a53f7708f427c43e9979e4eb /man
parentb0b46a2c12c4ba04ea2425d7930b14ca48bc6545 (diff)
downloadsystemd-3daffa82c421c538f279d7409f868de9311b6c53.tar.gz
doc: spell out handle-* options, use <literal> syntax (#5673)
Diffstat (limited to 'man')
-rw-r--r--man/logind.conf.xml10
1 files changed, 6 insertions, 4 deletions
diff --git a/man/logind.conf.xml b/man/logind.conf.xml
index 1d7b1becd0..16f51af72c 100644
--- a/man/logind.conf.xml
+++ b/man/logind.conf.xml
@@ -244,8 +244,9 @@
<para>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
+ (<literal>handle-power-key</literal>, <literal>handle-suspend-key</literal>,
+ <literal>handle-hibernate-key</literal>, <literal>handle-lid-switch</literal>).
+ 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 <varname>Handle*=</varname>
@@ -261,8 +262,9 @@
<listitem><para>Controls whether actions that <command>systemd-logind</command>
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-*-key" and "handle-lid-switch"), are always honored,
- irrespective of this setting.</para>
+ locks (<literal>handle-power-key</literal>, <literal>handle-suspend-key</literal>,
+ <literal>handle-hibernate-key</literal>, <literal>handle-lid-switch</literal>),
+ are always honored, irrespective of this setting.</para>
<para>These settings take boolean arguments. If <literal>no</literal>, the
inhibitor locks taken by applications are respected. If <literal>yes</literal>,