2012-05-05 02:34:48 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2012 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
2014-02-13 23:33:51 +04:00
<refentry id= "systemd-inhibit"
xmlns:xi="http://www.w3.org/2001/XInclude">
2012-05-05 02:34:48 +04:00
<refentryinfo >
<title > systemd-inhibit</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-inhibit</refentrytitle>
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-inhibit</refname>
<refpurpose > Execute a program with an inhibition lock taken</refpurpose>
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
<command > systemd-inhibit <arg choice= "opt" rep= "repeat" > OPTIONS</arg> <arg > COMMAND</arg> <arg choice= "opt" rep= "repeat" > ARGUMENTS</arg> </command>
</cmdsynopsis>
<cmdsynopsis >
<command > systemd-inhibit <arg choice= "opt" rep= "repeat" > OPTIONS</arg> --list</command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <command > systemd-inhibit</command> may be used
2012-05-05 02:46:31 +04:00
to execute a program with a shutdown, sleep or idle
2012-05-05 02:34:48 +04:00
inhibitor lock taken. The lock will be acquired before
the specified command line is executed and released
afterwards.</para>
<para > Inhibitor locks may be used to block or delay
2012-05-05 02:46:31 +04:00
system sleep and shutdown requests from the user, as well
as automatic idle handling of the OS. This is useful
2012-05-05 02:34:48 +04:00
to avoid system suspends while an optical disc is
being recorded, or similar operations that should not
be interrupted.</para>
2012-06-29 04:07:40 +04:00
<para > For more information see the <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/inhibit">Inhibitor
Lock Developer Documentation</ulink> .</para>
2012-05-05 02:34:48 +04:00
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
<varlistentry >
<term > <option > --what=</option> </term>
2013-06-27 23:51:44 +04:00
<listitem > <para > Takes a colon-separated
list of one or more
2012-05-05 02:34:48 +04:00
operations to inhibit:
<literal > shutdown</literal> ,
2012-05-05 02:46:31 +04:00
<literal > sleep</literal> ,
2012-09-19 17:28:55 +04:00
<literal > idle</literal> ,
<literal > handle-power-key</literal> ,
2012-10-03 05:48:19 +04:00
<literal > handle-suspend-key</literal> ,
<literal > handle-hibernate-key</literal> ,
2012-09-19 17:28:55 +04:00
<literal > handle-lid-switch</literal> ,
for inhibiting
2012-06-29 04:07:40 +04:00
reboot/power-off/halt/kexec,
2012-09-19 17:28:55 +04:00
suspending/hibernating, the automatic
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
idle detection, or the low-level
2012-09-19 17:28:55 +04:00
handling of the power/sleep key and
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
the lid switch, respectively. If omitted,
defaults to
2012-09-19 17:28:55 +04:00
<literal > idle:sleep:shutdown</literal> .</para> </listitem>
2012-05-05 02:34:48 +04:00
</varlistentry>
<varlistentry >
<term > <option > --who=</option> </term>
2013-06-27 23:51:44 +04:00
<listitem > <para > Takes a short,
human-readable descriptive string for the
program taking the lock. If not passed,
2012-05-05 02:34:48 +04:00
defaults to the command line
string.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --why=</option> </term>
2013-06-27 23:51:44 +04:00
<listitem > <para > Takes a short,
human-readable descriptive string for the
2012-05-05 02:34:48 +04:00
reason for taking the lock. Defaults
to "Unknown reason".</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --mode=</option> </term>
<listitem > <para > Takes either
<literal > block</literal> or
<literal > delay</literal> and describes
how the lock is applied. If
<literal > block</literal> is used (the
default), the lock prohibits any of
the requested operations without time
limit, and only privileged users may
override it. If
<literal > delay</literal> is used, the
lock can only delay the requested
operations for a limited time. If the
2013-06-27 23:51:44 +04:00
time elapses, the lock is ignored and
2012-05-05 02:34:48 +04:00
the operation executed. The time limit
may be specified in
2014-02-09 10:34:20 +04:00
<citerefentry > <refentrytitle > logind.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> . Note
2012-09-19 17:28:55 +04:00
that <literal > delay</literal> is only
2012-10-26 02:16:47 +04:00
available for <literal > sleep</literal>
2012-09-19 17:28:55 +04:00
and
<literal > shutdown</literal> .</para> </listitem>
2012-05-05 02:34:48 +04:00
</varlistentry>
<varlistentry >
<term > <option > --list</option> </term>
<listitem > <para > Lists all active
inhibition locks instead of acquiring
one.</para> </listitem>
</varlistentry>
2014-02-13 23:33:51 +04:00
<xi:include href= "standard-options.xml" xpointer= "help" />
<xi:include href= "standard-options.xml" xpointer= "version" />
2012-05-05 02:34:48 +04:00
</variablelist>
</refsect1>
<refsect1 >
<title > Exit status</title>
<para > Returns the exit status of the executed program.</para>
</refsect1>
2012-06-29 04:07:40 +04:00
<refsect1 >
<title > Example</title>
<programlisting > # systemd-inhibit wodim foobar.iso</programlisting>
<para > This burns the ISO image
<filename > foobar.iso</filename> on a CD using
<citerefentry > <refentrytitle > wodim</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
and inhibits system sleeping, shutdown and idle while
doing so.</para>
</refsect1>
2012-05-05 02:34:48 +04:00
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2014-02-09 10:34:20 +04:00
<citerefentry > <refentrytitle > logind.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2012-05-05 02:34:48 +04:00
</para>
</refsect1>
</refentry>