2010-05-16 05:06:41 +08:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2013-03-30 02:22:27 +08:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % entities SYSTEM "custom-entities.ent" >
%entities;
]>
2010-05-16 05:06:41 +08:00
<!--
This file is part of systemd.
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
2012-04-12 06:20:58 +08:00
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
2010-05-16 05:06:41 +08:00
(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
2012-04-12 06:20:58 +08:00
Lesser General Public License for more details.
2010-05-16 05:06:41 +08:00
2012-04-12 06:20:58 +08:00
You should have received a copy of the GNU Lesser General Public License
2010-05-16 05:06:41 +08:00
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
<refentry id= "systemd.unit" >
<refentryinfo >
<title > systemd.unit</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.unit</refentrytitle>
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd.unit</refname>
2012-07-17 00:08:25 +08:00
<refpurpose > Unit configuration</refpurpose>
2010-05-16 05:06:41 +08:00
</refnamediv>
<refsynopsisdiv >
2013-02-04 11:23:53 +08:00
<para > <filename > <replaceable > service</replaceable> .service</filename> ,
<filename > <replaceable > socket</replaceable> .socket</filename> ,
<filename > <replaceable > device</replaceable> .device</filename> ,
<filename > <replaceable > mount</replaceable> .mount</filename> ,
<filename > <replaceable > automount</replaceable> .automount</filename> ,
<filename > <replaceable > swap</replaceable> .swap</filename> ,
<filename > <replaceable > target</replaceable> .target</filename> ,
<filename > <replaceable > path</replaceable> .path</filename> ,
<filename > <replaceable > timer</replaceable> .timer</filename> ,
2013-07-24 23:31:17 +08:00
<filename > <replaceable > snapshot</replaceable> .snapshot</filename> ,
<filename > <replaceable > slice</replaceable> .slice</filename> ,
<filename > <replaceable > scope</replaceable> .scope</filename> </para>
2013-02-04 11:23:53 +08:00
<para > <literallayout > <filename > /etc/systemd/system/*</filename>
<filename > /run/systemd/system/*</filename>
<filename > /usr/lib/systemd/system/*</filename>
<filename > ...</filename>
</literallayout> </para>
2013-07-24 23:31:44 +08:00
<para > <literallayout > <filename > $HOME/.config/systemd/user/*</filename>
<filename > /etc/systemd/user/*</filename>
2013-02-04 11:23:53 +08:00
<filename > /run/systemd/user/*</filename>
<filename > /usr/lib/systemd/user/*</filename>
<filename > ...</filename>
</literallayout> </para>
2010-05-16 05:06:41 +08:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > A unit configuration file encodes information
2010-06-24 23:22:52 +08:00
about a service, a socket, a device, a mount point, an
2010-06-24 23:25:16 +08:00
automount point, a swap file or partition, a start-up
2013-07-24 23:31:17 +08:00
target, a watched file system path, a timer controlled
and supervised by
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
a temporary system state snapshot, a resource
management slice or a group of externally created
processes. The syntax is inspired by <ulink
2010-06-25 01:08:38 +08:00
url="http://standards.freedesktop.org/desktop-entry-spec/latest/">XDG
2013-07-24 23:31:17 +08:00
Desktop Entry Specification</ulink>
<filename > .desktop</filename> files, which are in turn
2010-06-25 01:08:38 +08:00
inspired by Microsoft Windows
<filename > .ini</filename> files.</para>
2010-05-16 05:06:41 +08:00
2012-10-26 06:16:47 +08:00
<para > This man page lists the common configuration
2010-07-09 02:06:24 +08:00
options of all the unit types. These options need to
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-16 02:59:12 +08:00
be configured in the [Unit] or [Install]
sections of the unit files.</para>
2010-06-25 01:08:38 +08:00
<para > In addition to the generic [Unit] and [Install]
2013-01-11 07:21:06 +08:00
sections described here, each unit may have a
2010-06-25 01:08:38 +08:00
type-specific section, e.g. [Service] for a service
unit. See the respective man pages for more
2013-02-04 11:23:53 +08:00
information:
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.device</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.mount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.automount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.swap</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.target</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.path</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.timer</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.snapshot</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
2013-07-24 23:31:17 +08:00
<citerefentry > <refentrytitle > systemd.slice</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
<citerefentry > <refentrytitle > systemd.scope</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
2013-02-04 11:23:53 +08:00
</para>
<para > Unit files are loaded from a set of paths
determined during compilation, described in the next section.
</para>
2010-06-25 01:08:38 +08:00
<para > Unit files may contain additional options on top
of those listed here. If systemd encounters an unknown
option it will write a warning log message but
continue loading the unit. If an option is prefixed
with <option > X-</option> it is ignored completely by
systemd. Applications may use this to include
additional information in the unit files.</para>
<para > Boolean arguments used in unit files can be
2010-07-02 23:19:52 +08:00
written in various formats. For positive settings the
2010-06-25 01:08:38 +08:00
strings <option > 1</option> , <option > yes</option> ,
<option > true</option> and <option > on</option> are
equivalent. For negative settings the strings
<option > 0</option> , <option > no</option> ,
<option > false</option> and <option > off</option> are
equivalent.</para>
2010-07-02 01:39:35 +08:00
<para > Time span values encoded in unit files can be
written in various formats. A stand-alone number
specifies a time in seconds. If suffixed with a time
2013-01-11 07:21:06 +08:00
unit, the unit is honored. A concatenation of multiple
values with units is supported, in which case the
values are added up. Example: "50" refers to 50
2010-07-02 01:39:35 +08:00
seconds; "2min 200ms" refers to 2 minutes plus 200
milliseconds, i.e. 120200ms. The following time units
2013-01-11 07:21:06 +08:00
are understood: s, min, h, d, w, ms, us. For details
see
<citerefentry > <refentrytitle > systemd.time</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> .</para>
2010-07-02 01:39:35 +08:00
2010-06-25 01:08:38 +08:00
<para > Empty lines and lines starting with # or ; are
2010-07-08 03:22:56 +08:00
ignored. This may be used for commenting. Lines ending
in a backslash are concatenated with the following
line while reading and the backslash is replaced by a
space character. This may be used to wrap long lines.</para>
2010-06-25 01:08:38 +08:00
<para > Along with a unit file
2013-01-11 07:21:06 +08:00
<filename > foo.service</filename> the directory
2010-06-25 01:08:38 +08:00
<filename > foo.service.wants/</filename> may exist. All
2013-01-11 07:21:06 +08:00
unit files symlinked from such a directory are
implicitly added as dependencies of type
2010-06-25 01:08:38 +08:00
<varname > Wanted=</varname> to the unit. This is useful
to hook units into the start-up of other units,
2013-01-11 07:21:06 +08:00
without having to modify their unit files. For details
about the semantics of <varname > Wanted=</varname> see
below. The preferred way to create symlinks in the
<filename > .wants/</filename> directory of a unit file
is with the <command > enable</command> command of the
2010-07-24 06:53:33 +08:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2010-06-25 01:08:38 +08:00
tool which reads information from the [Install]
2013-01-11 07:21:06 +08:00
section of unit files (see below). A similar
2011-03-18 10:32:47 +08:00
functionality exists for <varname > Requires=</varname>
type dependencies as well, the directory suffix is
<filename > .requires/</filename> in this case.</para>
2010-06-25 01:08:38 +08:00
2013-01-11 07:21:06 +08:00
<para > Along with a unit file
<filename > foo.service</filename> a directory
<filename > foo.service.d/</filename> may exist. All
2013-07-12 11:39:27 +08:00
files with the suffix <literal > .conf</literal> from
2013-01-11 07:21:06 +08:00
this directory will be parsed after the file itself is
parsed. This is useful to alter or add configuration
settings to a unit, without having to modify their
unit files. Make sure that the file that is included
has the appropriate section headers before any
directive.</para>
<para > If a line starts with <option > .include</option>
2013-06-28 03:51:44 +08:00
followed by a filename, the specified file will be
2013-01-11 07:21:06 +08:00
parsed at this point. Make sure that the file that is
included has the appropriate section headers before
any directives.</para>
2010-06-25 01:08:38 +08:00
<para > Note that while systemd offers a flexible
dependency system between units it is recommended to
2013-01-29 11:10:50 +08:00
use this functionality only sparingly and instead rely
2010-06-25 01:08:38 +08:00
on techniques such as bus-based or socket-based
2013-01-29 11:10:50 +08:00
activation which make dependencies implicit, resulting
in a both simpler and more flexible system.</para>
2010-07-02 05:49:50 +08:00
<para > Some unit names reflect paths existing in the
2013-05-18 17:28:25 +08:00
file system namespace. Example: a device unit
2010-07-02 05:49:50 +08:00
<filename > dev-sda.device</filename> refers to a device
2013-05-03 12:55:20 +08:00
with the device node <filename noindex= 'true' > /dev/sda</filename> in
2010-07-02 05:49:50 +08:00
the file system namespace. If this applies a special
2010-07-09 03:48:09 +08:00
way to escape the path name is used, so that the
2013-06-28 03:51:44 +08:00
result is usable as part of a filename. Basically,
2010-07-09 03:48:09 +08:00
given a path, "/" is replaced by "-", and all
unprintable characters and the "-" are replaced by
C-style "\x20" escapes. The root directory "/" is
encoded as single dash, while otherwise the initial
and ending "/" is removed from all paths during
transformation. This escaping is reversible.</para>
2010-07-02 05:49:50 +08:00
<para > Optionally, units may be instantiated from a
template file at runtime. This allows creation of
multiple units from a single configuration file. If
systemd looks for a unit configuration file it will
first search for the literal unit name in the
filesystem. If that yields no success and the unit
2013-06-30 00:09:14 +08:00
name contains an <literal > @</literal> character, systemd will look for a
2010-07-02 05:49:50 +08:00
unit template that shares the same name but with the
2013-06-30 00:09:14 +08:00
instance string (i.e. the part between the <literal > @</literal> character
2010-07-02 05:49:50 +08:00
and the suffix) removed. Example: if a service
<filename > getty@tty3.service</filename> is requested
and no file by that name is found, systemd will look
for <filename > getty@.service</filename> and
instantiate a service from that configuration file if
2011-09-05 16:35:57 +08:00
it is found.</para>
<para > To refer to the instance string from
2010-07-02 05:49:50 +08:00
within the configuration file you may use the special
<literal > %i</literal> specifier in many of the
2013-01-11 07:21:06 +08:00
configuration options. See below for details.</para>
2010-09-15 03:52:33 +08:00
2010-10-09 00:21:52 +08:00
<para > If a unit file is empty (i.e. has the file size
0) or is symlinked to <filename > /dev/null</filename>
its configuration will not be loaded and it appears
with a load state of <literal > masked</literal> , and
cannot be activated. Use this as an effective way to
fully disable a unit, making it impossible to start it
even manually.</para>
2010-09-15 03:52:33 +08:00
<para > The unit file format is covered by the
<ulink
url="http://www.freedesktop.org/wiki/Software/systemd/InterfaceStabilityPromise">Interface
Stability Promise</ulink> .</para>
2013-01-11 07:21:06 +08:00
2010-05-16 05:06:41 +08:00
</refsect1>
2013-02-04 11:23:53 +08:00
<refsect1 >
2013-04-30 07:36:49 +08:00
<title > Unit Load Path</title>
2013-02-04 11:23:53 +08:00
<para > Unit files are loaded from a set of paths
determined during compilation, described in the two
2013-07-24 23:31:44 +08:00
tables below. Unit files found in directories listed
earlier override files with the same name in
directories lower in the list.</para>
2013-02-04 11:23:53 +08:00
2013-04-30 07:36:49 +08:00
<para > When systemd is running in user mode
2013-02-04 11:23:53 +08:00
(<option > --user</option> ) and the variable
<varname > $SYSTEMD_UNIT_PATH</varname> is set, this
contents of this variable overrides the unit load
path.
</para>
<table >
<title >
Load path when running in system mode (<option > --system</option> ).
</title>
<tgroup cols= '2' >
<colspec colname= 'path' />
<colspec colname= 'expl' />
<thead >
<row >
<entry > Path</entry>
<entry > Description</entry>
</row>
</thead>
<tbody >
<row >
<entry > <filename > /etc/systemd/system</filename> </entry>
2013-04-30 07:36:49 +08:00
<entry > Local configuration</entry>
2013-02-04 11:23:53 +08:00
</row>
<row >
2013-07-28 00:49:58 +08:00
<entry > <filename > /run/systemd/system</filename> </entry>
2013-07-24 23:31:44 +08:00
<entry > Runtime units</entry>
2013-02-04 11:23:53 +08:00
</row>
<row >
<entry > <filename > /usr/lib/systemd/system</filename> </entry>
2013-07-24 23:31:44 +08:00
<entry > Units of installed packages</entry>
2013-02-04 11:23:53 +08:00
</row>
</tbody>
</tgroup>
</table>
<table >
<title >
2013-07-24 23:31:37 +08:00
Load path when running in user mode (<option > --user</option> ).
2013-02-04 11:23:53 +08:00
</title>
<tgroup cols= '2' >
<colspec colname= 'path' />
<colspec colname= 'expl' />
<thead >
<row >
<entry > Path</entry>
<entry > Description</entry>
</row>
</thead>
<tbody >
<row >
2013-07-24 23:31:44 +08:00
<entry > <filename > $HOME/.config/systemd/user</filename> </entry>
<entry > User configuration</entry>
2013-02-04 11:23:53 +08:00
</row>
<row >
<entry > <filename > /etc/systemd/user</filename> </entry>
2013-04-30 07:36:49 +08:00
<entry > Local configuration</entry>
2013-02-04 11:23:53 +08:00
</row>
<row >
<entry > <filename > /run/systemd/user</filename> </entry>
2013-07-24 23:31:44 +08:00
<entry > Runtime units</entry>
2013-02-04 11:23:53 +08:00
</row>
<row >
<entry > <filename > /usr/lib/systemd/user</filename> </entry>
2013-07-24 23:31:44 +08:00
<entry > Units of installed packages</entry>
2013-02-04 11:23:53 +08:00
</row>
</tbody>
</tgroup>
</table>
<para > Additional units might be loaded into systemd
("linked") from directories not on the unit load
path. See the <command > link</command> command for
2013-07-24 23:31:44 +08:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> . Also,
some units are dynamically created via generators
<ulink
url="http://www.freedesktop.org/wiki/Software/systemd/Generators/">Generators</ulink> .
2013-02-04 11:23:53 +08:00
</para>
</refsect1>
2010-05-16 05:06:41 +08:00
<refsect1 >
<title > Options</title>
2010-06-24 23:22:52 +08:00
<para > Unit file may include a [Unit] section, which
carries generic information about the unit that is not
dependent on the type of unit:</para>
2013-01-26 23:47:16 +08:00
<variablelist class= 'unit-directives' >
2010-06-25 01:08:38 +08:00
<varlistentry >
<term > <varname > Description=</varname> </term>
<listitem > <para > A free-form string
2010-07-04 01:54:00 +08:00
describing the unit. This is intended
for use in UIs to show descriptive
information along with the unit
2013-08-13 03:59:41 +08:00
name. The description should contain a name
that means something to the end user.
<literal > Apache2 Web Server</literal> is a good
example. Bad examples are
<literal > high-performance light-weight HTTP
server</literal> (too generic) or
<literal > Apache2</literal> (too specific and
meaningless for people who do not know
Apache).</para> </listitem>
2010-06-25 01:08:38 +08:00
</varlistentry>
2012-05-21 21:12:18 +08:00
<varlistentry >
<term > <varname > Documentation=</varname> </term>
2013-06-28 03:51:44 +08:00
<listitem > <para > A space-separated list
2012-05-21 21:12:18 +08:00
of URIs referencing documentation for
this unit or its
configuration. Accepted are only URIs
of the types
<literal > http://</literal> ,
<literal > https://</literal> ,
<literal > file:</literal> ,
<literal > info:</literal> ,
<literal > man:</literal> . For more
information about the syntax of these
2013-06-28 03:51:44 +08:00
URIs, see
2012-10-31 07:06:08 +08:00
<citerefentry > <refentrytitle > uri</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> . The
URIs should be listed in order of
relevance, starting with the most
relevant. It is a good idea to first
reference documentation that explains
what the unit's purpose is, followed
by how it is configured, followed by
2013-01-17 09:27:06 +08:00
any other related documentation. This
option may be specified more than once
in which case the specified list of
URIs is merged. If the empty string is
2013-06-28 03:51:44 +08:00
assigned to this option, the list is
2013-01-17 09:27:06 +08:00
reset and all prior assignments will
have no effect.</para> </listitem>
2012-05-21 21:12:18 +08:00
</varlistentry>
2010-05-16 05:06:41 +08:00
<varlistentry >
2010-05-17 04:45:11 +08:00
<term > <varname > Requires=</varname> </term>
2010-06-24 23:22:52 +08:00
2010-06-25 01:08:38 +08:00
<listitem > <para > Configures requirement
2010-06-24 23:22:52 +08:00
dependencies on other units. If this
2010-07-09 02:06:24 +08:00
unit gets activated, the units listed
2010-06-24 23:22:52 +08:00
here will be activated as well. If one
of the other units gets deactivated or
its activation fails, this unit will
be deactivated. This option may be
specified more than once, in which
case requirement dependencies for all
2010-06-25 01:08:38 +08:00
listed names are created. Note that
requirement dependencies do not
influence the order in which services
are started or stopped. This has to be
configured independently with the
<varname > After=</varname> or
<varname > Before=</varname> options. If
a unit
<filename > foo.service</filename>
requires a unit
<filename > bar.service</filename> as
configured with
<varname > Requires=</varname> and no
ordering is configured with
<varname > After=</varname> or
<varname > Before=</varname> , then both
units will be started simultaneously
and without any delay between them if
<filename > foo.service</filename> is
activated. Often it is a better choice
to use <varname > Wants=</varname>
instead of
<varname > Requires=</varname> in order
to achieve a system that is more
robust when dealing with failing
2011-07-13 20:13:31 +08:00
services.</para>
<para > Note that dependencies of this
type may also be configured outside of
the unit configuration file by
adding a symlink to a
<filename > .requires/</filename> directory
accompanying the unit file. For
details see above.</para> </listitem>
2010-05-16 05:06:41 +08:00
</varlistentry>
2010-06-25 01:08:38 +08:00
<varlistentry >
<term > <varname > RequiresOverridable=</varname> </term>
<listitem > <para > Similar to
<varname > Requires=</varname> .
Dependencies listed in
<varname > RequiresOverridable=</varname>
which cannot be fulfilled or fail to
2010-07-09 02:06:24 +08:00
start are ignored if the startup was
2010-06-25 01:08:38 +08:00
explicitly requested by the user. If
the start-up was pulled in indirectly
by some dependency or automatic
start-up of units that is not
requested by the user this dependency
must be fulfilled and otherwise the
transaction fails. Hence, this option
may be used to configure dependencies
2010-06-25 06:06:49 +08:00
that are normally honored unless the
2010-06-25 01:08:38 +08:00
user explicitly starts up the unit, in
which case whether they failed or not
is irrelevant.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > Requisite=</varname> </term>
<term > <varname > RequisiteOverridable=</varname> </term>
<listitem > <para > Similar to
<varname > Requires=</varname>
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-16 02:59:12 +08:00
and <varname > RequiresOverridable=</varname> , respectively. However,
2010-06-25 01:08:38 +08:00
if a unit listed here is not started
already it will not be started and the
transaction fails
immediately.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <varname > Wants=</varname> </term>
<listitem > <para > A weaker version of
<varname > Requires=</varname> . A unit
listed in this option will be started
if the configuring unit is. However,
2010-07-09 02:06:24 +08:00
if the listed unit fails to start up
2010-06-25 01:08:38 +08:00
or cannot be added to the transaction
this has no impact on the validity of
the transaction as a whole. This is
the recommended way to hook start-up
of one unit to the start-up of another
2011-07-13 20:13:31 +08:00
unit.</para>
<para > Note that dependencies of this
2010-06-25 01:08:38 +08:00
type may also be configured outside of
the unit configuration file by
adding a symlink to a
<filename > .wants/</filename> directory
accompanying the unit file. For
details see above.</para> </listitem>
</varlistentry>
2010-10-29 05:18:47 +08:00
<varlistentry >
2012-07-14 05:34:40 +08:00
<term > <varname > BindsTo=</varname> </term>
2010-10-29 05:18:47 +08:00
<listitem > <para > Configures requirement
dependencies, very similar in style to
<varname > Requires=</varname> , however
2012-09-05 01:24:16 +08:00
in addition to this behavior it also
2010-10-29 05:18:47 +08:00
declares that this unit is stopped
when any of the units listed suddenly
disappears. Units can suddenly,
unexpectedly disappear if a service
terminates on its own choice, a device
is unplugged or a mount point
2010-11-18 01:38:29 +08:00
unmounted without involvement of
2010-10-29 05:18:47 +08:00
systemd.</para> </listitem>
</varlistentry>
2012-07-20 21:55:01 +08:00
<varlistentry >
<term > <varname > PartOf=</varname> </term>
2012-07-26 15:34:27 +08:00
<listitem > <para > Configures dependencies
similar to <varname > Requires=</varname> ,
but limited to stopping and restarting
of units. When systemd stops or restarts
the units listed here, the action is
propagated to this unit.
Note that this is a one way dependency -
changes to this unit do not affect the
listed units.
</para> </listitem>
2012-07-20 21:55:01 +08:00
</varlistentry>
2010-06-25 01:08:38 +08:00
<varlistentry >
<term > <varname > Conflicts=</varname> </term>
<listitem > <para > Configures negative
requirement dependencies. If a unit
2010-07-09 02:06:24 +08:00
has a
2010-06-25 01:08:38 +08:00
<varname > Conflicts=</varname> setting
2010-07-09 02:06:24 +08:00
on another unit, starting the former
2010-06-25 01:08:38 +08:00
will stop the latter and vice
versa. Note that this setting is
independent of and orthogonal to the
<varname > After=</varname> and
<varname > Before=</varname> ordering
2010-08-10 04:32:30 +08:00
dependencies.</para>
<para > If a unit A that conflicts with
a unit B is scheduled to be started at
the same time as B, the transaction
will either fail (in case both are
required part of the transaction) or
be modified to be fixed (in case one
or both jobs are not a required part
of the transaction). In the latter
case the job that is not the required
will be removed, or in case both are
not required the unit that conflicts
will be started and the unit that is
conflicted is
stopped.</para> </listitem>
2010-06-25 01:08:38 +08:00
</varlistentry>
<varlistentry >
<term > <varname > Before=</varname> </term>
<term > <varname > After=</varname> </term>
<listitem > <para > Configures ordering
dependencies between units. If a unit
<filename > foo.service</filename>
contains a setting
<option > Before=bar.service</option>
2010-07-09 02:06:24 +08:00
and both units are being started,
2010-06-25 01:08:38 +08:00
<filename > bar.service</filename> 's
start-up is delayed until
<filename > foo.service</filename> is
started up. Note that this setting is
independent of and orthogonal to the
requirement dependencies as configured
by <varname > Requires=</varname> . It is
a common pattern to include a unit
name in both the
<varname > After=</varname> and
<varname > Requires=</varname> option in
which case the unit listed will be
started before the unit that is
configured with these options. This
option may be specified more than
once, in which case ordering
dependencies for all listed names are
created. <varname > After=</varname> is
the inverse of
<varname > Before=</varname> , i.e. while
<varname > After=</varname> ensures that
the configured unit is started after
the listed unit finished starting up,
<varname > Before=</varname> ensures the
opposite, i.e. that the configured
unit is fully started up before the
listed unit is started. Note that when
two units with an ordering dependency
between them are shut down, the
2010-07-09 02:06:24 +08:00
inverse of the start-up order is
2010-06-25 01:08:38 +08:00
applied. i.e. if a unit is configured
with <varname > After=</varname> on
another unit, the former is stopped
before the latter if both are shut
down. If one unit with an ordering
dependency on another unit is shut
down while the latter is started up,
the shut down is ordered before the
start-up regardless whether the
ordering dependency is actually of
type <varname > After=</varname> or
<varname > Before=</varname> . If two
units have no ordering dependencies
between them they are shut down
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-16 02:59:12 +08:00
or started up simultaneously, and
2010-06-25 01:08:38 +08:00
no ordering takes
place. </para> </listitem>
</varlistentry>
2010-07-18 08:11:38 +08:00
<varlistentry >
<term > <varname > OnFailure=</varname> </term>
<listitem > <para > Lists one or more
units that are activated when this
2010-08-31 06:17:56 +08:00
unit enters the
2013-06-26 20:03:53 +08:00
<literal > failed</literal>
2010-08-31 06:17:56 +08:00
state.</para> </listitem>
2010-07-18 08:11:38 +08:00
</varlistentry>
2012-01-11 09:47:14 +08:00
<varlistentry >
2012-07-14 05:34:40 +08:00
<term > <varname > PropagatesReloadTo=</varname> </term>
<term > <varname > ReloadPropagatedFrom=</varname> </term>
2012-01-11 09:47:14 +08:00
<listitem > <para > Lists one or more
units where reload requests on the
unit will be propagated to/on the
other unit will be propagated
from. Issuing a reload request on a
unit will automatically also enqueue a
reload request on all units that the
reload request shall be propagated to
via these two
settings.</para> </listitem>
</varlistentry>
2012-04-29 20:26:07 +08:00
<varlistentry >
<term > <varname > RequiresMountsFor=</varname> </term>
2013-06-28 03:51:44 +08:00
<listitem > <para > Takes a space-separated
list of absolute paths. Automatically
2012-04-29 20:26:07 +08:00
adds dependencies of type
<varname > Requires=</varname> and
<varname > After=</varname> for all
mount units required to access the
specified path.</para> </listitem>
</varlistentry>
2011-04-07 10:11:31 +08:00
<varlistentry >
<term > <varname > OnFailureIsolate=</varname> </term>
<listitem > <para > Takes a boolean
argument. If <option > true</option> the
unit listed in
<varname > OnFailure=</varname> will be
enqueued in isolation mode, i.e. all
units that are not its dependency will
be stopped. If this is set only a
single unit may be listed in
<varname > OnFailure=</varname> . Defaults
to
<option > false</option> .</para> </listitem>
</varlistentry>
2011-04-14 09:55:03 +08:00
<varlistentry >
<term > <varname > IgnoreOnIsolate=</varname> </term>
<listitem > <para > Takes a boolean
argument. If <option > true</option>
this unit will not be stopped when
isolating another unit. Defaults to
<option > false</option> .</para> </listitem>
</varlistentry>
2011-05-05 16:58:55 +08:00
<varlistentry >
<term > <varname > IgnoreOnSnapshot=</varname> </term>
<listitem > <para > Takes a boolean
argument. If <option > true</option>
this unit will not be included in
snapshots. Defaults to
2011-07-12 04:09:41 +08:00
<option > true</option> for device and
snapshot units, <option > false</option>
2011-05-05 16:58:55 +08:00
for the others.</para> </listitem>
</varlistentry>
2010-06-25 01:08:38 +08:00
<varlistentry >
<term > <varname > StopWhenUnneeded=</varname> </term>
<listitem > <para > Takes a boolean
argument. If <option > true</option>
this unit will be stopped when it is
no longer used. Note that in order to
2010-07-09 02:06:24 +08:00
minimize the work to be executed,
systemd will not stop units by default
2010-06-25 01:08:38 +08:00
unless they are conflicting with other
units, or the user explicitly
requested their shut down. If this
2010-07-09 02:06:24 +08:00
option is set, a unit will be
2010-06-25 01:08:38 +08:00
automatically cleaned up if no other
active unit requires it. Defaults to
<option > false</option> .</para> </listitem>
</varlistentry>
<varlistentry >
2010-08-11 02:57:21 +08:00
<term > <varname > RefuseManualStart=</varname> </term>
<term > <varname > RefuseManualStop=</varname> </term>
2010-06-25 01:08:38 +08:00
<listitem > <para > Takes a boolean
argument. If <option > true</option>
2010-07-09 02:06:24 +08:00
this unit can only be activated
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-16 02:59:12 +08:00
or deactivated indirectly. In
2010-08-11 02:57:21 +08:00
this case explicit start-up
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-16 02:59:12 +08:00
or termination requested by the
2010-08-11 02:57:21 +08:00
user is denied, however if it is
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-16 02:59:12 +08:00
started or stopped as a
2010-07-09 02:06:24 +08:00
dependency of another unit, start-up
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-16 02:59:12 +08:00
or termination will succeed. This
2010-08-11 02:57:21 +08:00
is mostly a safety feature to ensure
that the user does not accidentally
activate units that are not intended
to be activated explicitly, and not
accidentally deactivate units that are
not intended to be deactivated.
These options default to
2010-06-25 01:08:38 +08:00
<option > false</option> .</para> </listitem>
</varlistentry>
2010-08-31 04:45:46 +08:00
<varlistentry >
<term > <varname > AllowIsolate=</varname> </term>
<listitem > <para > Takes a boolean
argument. If <option > true</option>
this unit may be used with the
<command > systemctl isolate</command>
command. Otherwise this will be
refused. It probably is a good idea to
leave this disabled except for target
units that shall be used similar to
runlevels in SysV init systems, just
as a precaution to avoid unusable
system states. This option defaults to
<option > false</option> .</para> </listitem>
</varlistentry>
2010-07-04 01:54:00 +08:00
<varlistentry >
<term > <varname > DefaultDependencies=</varname> </term>
<listitem > <para > Takes a boolean
argument. If <option > true</option>
(the default), a few default
dependencies will implicitly be
created for the unit. The actual
dependencies created depend on the
unit type. For example, for service
units, these dependencies ensure that
the service is started only after
basic system initialization is
2010-07-09 02:06:24 +08:00
completed and is properly terminated on
2010-07-04 01:54:00 +08:00
system shutdown. See the respective
man pages for details. Generally, only
services involved with early boot or
late shutdown should set this option
to <option > false</option> . It is
highly recommended to leave this
option enabled for the majority of
common units. If set to
2013-07-02 11:44:04 +08:00
<option > false</option> , this option
2010-07-04 01:54:00 +08:00
does not disable all implicit
dependencies, just non-essential
ones.</para> </listitem>
</varlistentry>
2010-07-18 08:11:38 +08:00
<varlistentry >
<term > <varname > JobTimeoutSec=</varname> </term>
<listitem > <para > When clients are
waiting for a job of this unit to
complete, time out after the specified
time. If this time limit is reached
the job will be cancelled, the unit
however will not change state or even
2013-06-26 20:03:53 +08:00
enter the <literal > failed</literal>
2010-08-31 06:17:56 +08:00
mode. This value defaults to 0 (job
timeouts disabled), except for device
units. NB: this timeout is independent
from any unit-specific timeout (for
example, the timeout set with
2010-07-18 08:11:38 +08:00
<varname > Timeout=</varname> in service
2010-08-31 06:17:56 +08:00
units) as the job timeout has no
effect on the unit itself, only on the
job that might be pending for it. Or
in other words: unit-specific timeouts
2010-07-18 08:11:38 +08:00
are useful to abort unit state
changes, and revert them. The job
timeout set with this option however
2010-08-31 06:17:56 +08:00
is useful to abort only the job
waiting for the unit state to
change.</para> </listitem>
2010-07-18 08:11:38 +08:00
</varlistentry>
2010-10-13 08:15:41 +08:00
<varlistentry >
<term > <varname > ConditionPathExists=</varname> </term>
2011-07-07 08:07:39 +08:00
<term > <varname > ConditionPathExistsGlob=</varname> </term>
2011-04-01 06:42:57 +08:00
<term > <varname > ConditionPathIsDirectory=</varname> </term>
2011-09-21 07:29:38 +08:00
<term > <varname > ConditionPathIsSymbolicLink=</varname> </term>
2011-09-21 06:44:51 +08:00
<term > <varname > ConditionPathIsMountPoint=</varname> </term>
2012-04-12 08:39:02 +08:00
<term > <varname > ConditionPathIsReadWrite=</varname> </term>
2010-11-16 03:06:49 +08:00
<term > <varname > ConditionDirectoryNotEmpty=</varname> </term>
2012-09-11 07:29:46 +08:00
<term > <varname > ConditionFileNotEmpty=</varname> </term>
2011-07-12 10:25:02 +08:00
<term > <varname > ConditionFileIsExecutable=</varname> </term>
2010-10-13 08:15:41 +08:00
<term > <varname > ConditionKernelCommandLine=</varname> </term>
2011-02-22 05:07:55 +08:00
<term > <varname > ConditionVirtualization=</varname> </term>
2011-04-04 00:17:05 +08:00
<term > <varname > ConditionSecurity=</varname> </term>
2011-10-11 21:16:52 +08:00
<term > <varname > ConditionCapability=</varname> </term>
2012-08-22 07:51:53 +08:00
<term > <varname > ConditionHost=</varname> </term>
2012-12-25 23:29:51 +08:00
<term > <varname > ConditionACPower=</varname> </term>
2010-11-11 05:28:19 +08:00
<term > <varname > ConditionNull=</varname> </term>
2010-10-13 08:15:41 +08:00
<listitem > <para > Before starting a unit
verify that the specified condition is
2012-08-22 07:51:53 +08:00
true. If it is not true the starting
of the unit will be skipped, however
all ordering dependencies of it are
still respected. A failing condition
will not result in the unit being
moved into a failure state. The
condition is checked at the time the
queued start job is to be
executed.</para>
<para > With
2010-10-13 08:15:41 +08:00
<varname > ConditionPathExists=</varname>
2012-08-22 07:51:53 +08:00
a file existence condition is
2010-10-13 08:15:41 +08:00
checked before a unit is started. If
the specified absolute path name does
2012-08-22 07:51:53 +08:00
not exist the condition will
fail. If the absolute path name passed
to
2010-10-13 08:15:41 +08:00
<varname > ConditionPathExists=</varname>
is prefixed with an exclamation mark
2013-06-26 20:03:53 +08:00
(<literal > !</literal> ), the test is negated, and the unit
2011-09-20 18:28:22 +08:00
is only started if the path does not
2012-08-22 07:51:53 +08:00
exist.</para>
<para > <varname > ConditionPathExistsGlob=</varname>
is similar to
<varname > ConditionPathExists=</varname> ,
but checks for the existence of at
least one file or directory matching
the specified globbing pattern.</para>
<para > <varname > ConditionPathIsDirectory=</varname>
2011-09-21 06:44:51 +08:00
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether a certain path
2011-09-21 07:07:25 +08:00
exists and is a
2012-08-22 07:51:53 +08:00
directory.</para>
<para > <varname > ConditionPathIsSymbolicLink=</varname>
2011-09-21 07:29:38 +08:00
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether a certain path
2011-09-23 23:09:49 +08:00
exists and is a symbolic
2012-08-22 07:51:53 +08:00
link.</para>
<para > <varname > ConditionPathIsMountPoint=</varname>
2011-09-21 06:44:51 +08:00
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether a certain path
exists and is a mount
2012-08-22 07:51:53 +08:00
point.</para>
<para > <varname > ConditionPathIsReadWrite=</varname>
2012-04-12 08:39:02 +08:00
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether the underlying
2012-08-22 07:51:53 +08:00
file system is readable and writable
2012-04-12 08:39:02 +08:00
(i.e. not mounted
2012-08-22 07:51:53 +08:00
read-only).</para>
2012-09-11 07:29:46 +08:00
<para > <varname > ConditionDirectoryNotEmpty=</varname>
2011-09-21 06:44:51 +08:00
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether a certain path
2012-09-11 07:29:46 +08:00
exists and is a non-empty
directory.</para>
2012-08-22 07:51:53 +08:00
2012-09-11 07:29:46 +08:00
<para > <varname > ConditionFileNotEmpty=</varname>
2011-04-01 06:42:57 +08:00
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether a certain path
2012-09-11 07:29:46 +08:00
exists and refers to a regular file
with a non-zero size.</para>
<para > <varname > ConditionFileIsExecutable=</varname>
is similar to
<varname > ConditionPathExists=</varname>
but verifies whether a certain path
exists, is a regular file and marked
executable.</para>
2012-08-22 07:51:53 +08:00
2012-09-11 07:29:46 +08:00
<para > Similar,
2010-10-13 08:15:41 +08:00
<varname > ConditionKernelCommandLine=</varname>
may be used to check whether a
specific kernel command line option is
set (or if prefixed with the
exclamation mark unset). The argument
must either be a single word, or an
2010-12-31 08:50:51 +08:00
assignment (i.e. two words, separated
2013-06-26 20:03:53 +08:00
<literal > =</literal> ). In the former
2010-11-11 05:28:19 +08:00
case the kernel command line is
searched for the word appearing as is,
or as left hand side of an
assignment. In the latter case the
exact assignment is looked for with
right and left hand side
2012-08-22 07:51:53 +08:00
matching.</para>
<para > <varname > ConditionVirtualization=</varname>
2011-02-22 05:07:55 +08:00
may be used to check whether the
system is executed in a virtualized
environment and optionally test
whether it is a specific
implementation. Takes either boolean
2011-03-08 10:04:47 +08:00
value to check if being executed in
2011-09-23 23:09:49 +08:00
any virtualized environment, or one of
<varname > vm</varname> and
2011-10-11 21:16:52 +08:00
<varname > container</varname> to test
2012-08-22 07:51:53 +08:00
against a generic type of
2011-10-11 21:16:52 +08:00
virtualization solution, or one of
2011-02-22 05:07:55 +08:00
<varname > qemu</varname> ,
<varname > kvm</varname> ,
<varname > vmware</varname> ,
<varname > microsoft</varname> ,
<varname > oracle</varname> ,
<varname > xen</varname> ,
2011-09-23 23:09:49 +08:00
<varname > bochs</varname> ,
<varname > chroot</varname> ,
2013-07-16 19:14:40 +08:00
<varname > uml</varname> ,
2011-09-23 10:38:39 +08:00
<varname > openvz</varname> ,
<varname > lxc</varname> ,
2012-01-25 07:13:05 +08:00
<varname > lxc-libvirt</varname> ,
2012-04-12 08:39:02 +08:00
<varname > systemd-nspawn</varname> to
test against a specific
implementation. If multiple
virtualization technologies are nested
only the innermost is considered. The
test may be negated by prepending an
2012-08-22 07:51:53 +08:00
exclamation mark.</para>
<para > <varname > ConditionSecurity=</varname>
2011-07-07 08:07:39 +08:00
may be used to check whether the given
security module is enabled on the
2013-05-12 04:40:08 +08:00
system. Currently the recognized values
2013-05-07 19:21:46 +08:00
values are <varname > selinux</varname> ,
2013-05-12 04:40:08 +08:00
<varname > apparmor</varname> ,
<varname > ima</varname> and
2013-05-07 19:21:46 +08:00
<varname > smack</varname> .
2011-07-07 08:07:39 +08:00
The test may be negated by prepending
2011-10-11 21:16:52 +08:00
an exclamation
2012-08-22 07:51:53 +08:00
mark.</para>
<para > <varname > ConditionCapability=</varname>
2011-10-11 21:16:52 +08:00
may be used to check whether the given
capability exists in the capability
bounding set of the service manager
(i.e. this does not check whether
capability is actually available in
the permitted or effective sets, see
<citerefentry > <refentrytitle > capabilities</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
for details). Pass a capability name
such as <literal > CAP_MKNOD</literal> ,
possibly prefixed with an exclamation
2012-08-22 07:51:53 +08:00
mark to negate the check.</para>
<para > <varname > ConditionHost=</varname>
may be used to match against the
2013-06-28 03:51:44 +08:00
hostname or machine ID of the
host. This either takes a hostname
2012-08-22 07:51:53 +08:00
string (optionally with shell style
globs) which is tested against the
2013-06-28 03:51:44 +08:00
locally set hostname as returned by
2012-08-22 07:51:53 +08:00
<citerefentry > <refentrytitle > gethostname</refentrytitle> <manvolnum > 2</manvolnum> </citerefentry> ,
or a machine ID formatted as string
(see
<citerefentry > <refentrytitle > machine-id</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ).
The test may be negated by prepending
an exclamation mark.</para>
2012-12-25 23:29:51 +08:00
<para > <varname > ConditionACPower=</varname>
2013-01-10 07:19:44 +08:00
may be used to check whether the
system has AC power, or is exclusively
2012-12-25 23:29:51 +08:00
battery powered at the time of
activation of the unit. This takes a
boolean argument. If set to
<varname > true</varname> the condition
will hold only if at least one AC
connector of the system is connected
to a power source, or if no AC
connectors are known. Conversely, if
set to <varname > false</varname> the
condition will hold only if there is
at least one AC connector known and
all AC connectors are disconnected
from a power source.</para>
2012-08-22 07:51:53 +08:00
<para > Finally,
2010-11-11 05:28:19 +08:00
<varname > ConditionNull=</varname> may
be used to add a constant condition
check value to the unit. It takes a
boolean argument. If set to
<varname > false</varname> the condition
will always fail, otherwise
2012-08-22 07:51:53 +08:00
succeed.</para>
<para > If multiple conditions are
2011-02-22 05:07:55 +08:00
specified the unit will be executed if
2011-03-08 10:04:47 +08:00
all of them apply (i.e. a logical AND
is applied). Condition checks can be
prefixed with a pipe symbol (|) in
which case a condition becomes a
triggering condition. If at least one
triggering condition is defined for a
unit then the unit will be executed if
at least one of the triggering
conditions apply and all of the
non-triggering conditions. If you
prefix an argument with the pipe
symbol and an exclamation mark the
pipe symbol must be passed first, the
2011-09-21 07:29:38 +08:00
exclamation second. Except for
<varname > ConditionPathIsSymbolicLink=</varname> ,
2013-01-17 09:27:06 +08:00
all path checks follow symlinks. If
any of these options is assigned the
empty string the list of conditions is
reset completely, all previous
condition settings (of any kind) will
have no effect.</para> </listitem>
2010-10-13 08:15:41 +08:00
</varlistentry>
2011-03-18 11:49:38 +08:00
2012-05-23 05:08:24 +08:00
<varlistentry >
<term > <varname > SourcePath=</varname> </term>
<listitem > <para > A path to a
configuration file this unit has been
generated from. This is primarily
useful for implementation of generator
tools that convert configuration from
an external configuration file format
into native unit files. Thus
functionality should not be used in
normal units.</para> </listitem>
</varlistentry>
2010-05-16 05:06:41 +08:00
</variablelist>
2010-06-24 23:22:52 +08:00
<para > Unit file may include a [Install] section, which
carries installation information for the unit. This
section is not interpreted by
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
during runtime. It is used exclusively by the
2010-07-24 06:53:33 +08:00
<command > enable</command> and
<command > disable</command> commands of the
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2010-06-25 01:08:38 +08:00
tool during installation of a unit:</para>
2010-06-24 23:22:52 +08:00
2013-01-26 23:47:16 +08:00
<variablelist class= 'unit-directives' >
2010-06-24 23:22:52 +08:00
<varlistentry >
<term > <varname > Alias=</varname> </term>
2010-07-02 23:28:02 +08:00
<listitem > <para > Additional names this
2010-06-24 23:22:52 +08:00
unit shall be installed under. The
names listed here must have the same
suffix (i.e. type) as the unit file
name. This option may be specified
more than once, in which case all
listed names are used. At installation
2010-06-25 06:04:29 +08:00
time,
2010-07-24 06:53:33 +08:00
<command > systemctl enable</command>
2010-06-24 23:22:52 +08:00
will create symlinks from these names
2013-06-28 03:51:44 +08:00
to the unit filename.</para> </listitem>
2010-06-25 01:08:38 +08:00
</varlistentry>
<varlistentry >
<term > <varname > WantedBy=</varname> </term>
2012-05-21 21:27:26 +08:00
<term > <varname > RequiredBy=</varname> </term>
2010-06-25 01:08:38 +08:00
2013-07-14 11:36:39 +08:00
<listitem > <para > A symbolic link is
created in the
<filename > .wants/</filename> or
2013-07-21 12:53:14 +08:00
<filename > .requires/</filename> directory
2013-07-14 11:36:39 +08:00
of the listed unit when this unit is
activated by <command > systemctl
enable</command> . This has the effect
that a dependency of type
<varname > Wants=</varname> or
<varname > Requires=</varname> is added
from the listed unit to the current
unit. The primary result is that the
current unit will be started when the
listed unit is started. See the
description of
<varname > Wants=</varname> and
<varname > Requires=</varname> in the
[Unit] section for details.</para>
<para > <command > WantedBy=foo.service</command>
2010-06-25 01:08:38 +08:00
in a service
<filename > bar.service</filename> is
mostly equivalent to
<command > Alias=foo.service.wants/bar.service</command>
2013-07-14 11:36:39 +08:00
in the same file. In case of template
units, <command > systemctl enable</command>
must be called with an instance name, and
this instance will be added to the
<filename > .wants/</filename> or
<filename > .requires/</filename> list
of the listed unit.
E.g. <command > WantedBy=getty.target</command>
in a service
<filename > getty@.service</filename>
will result in <command > systemctl
enable getty@tty2.service</command>
creating a
<filename > getty.target.wants/getty@tty2.service</filename>
link to <filename > getty@.service</filename> .
</para> </listitem>
2010-06-25 01:08:38 +08:00
</varlistentry>
<varlistentry >
<term > <varname > Also=</varname> </term>
<listitem > <para > Additional units to
2013-05-07 04:47:41 +08:00
install/deinstall when this unit is
installed/deinstalled. If the user
requests installation/deinstallation
of a unit with this option configured,
2010-07-24 06:53:33 +08:00
<command > systemctl enable</command>
2013-05-07 04:47:41 +08:00
and <command > systemctl
disable</command> will automatically
install/uninstall units listed in this option as
2010-06-25 01:08:38 +08:00
well.</para> </listitem>
2010-06-24 23:22:52 +08:00
</varlistentry>
</variablelist>
2013-01-28 12:11:31 +08:00
<para > The following specifiers are interpreted in the
2013-07-19 14:45:27 +08:00
Install section: %n, %N, %p, %i, %U, %u, %m, %H, %b, %v.
2013-01-28 12:11:31 +08:00
For their meaning see the next section.
</para>
2010-05-16 05:06:41 +08:00
</refsect1>
2013-01-11 07:21:06 +08:00
<refsect1 >
<title > Specifiers</title>
<para > Many settings resolve specifiers which may be
used to write generic unit files referring to runtime
or unit parameters that are replaced when the unit
files are loaded. The following specifiers are
understood:</para>
<table >
<title > Specifiers available in unit files</title>
<tgroup cols= '3' align= 'left' colsep= '1' rowsep= '1' >
<colspec colname= "spec" />
<colspec colname= "mean" />
<colspec colname= "detail" />
<thead >
<row >
<entry > Specifier</entry>
<entry > Meaning</entry>
<entry > Details</entry>
</row>
</thead>
<tbody >
<row >
<entry > <literal > %n</literal> </entry>
<entry > Full unit name</entry>
<entry > </entry>
</row>
<row >
<entry > <literal > %N</literal> </entry>
<entry > Unescaped full unit name</entry>
<entry > </entry>
</row>
<row >
<entry > <literal > %p</literal> </entry>
<entry > Prefix name</entry>
<entry > For instantiated units this refers to the string before the @. For non-instantiated units this refers to to the name of the unit with the type suffix removed.</entry>
</row>
<row >
<entry > <literal > %P</literal> </entry>
<entry > Unescaped prefix name</entry>
<entry > </entry>
</row>
<row >
<entry > <literal > %i</literal> </entry>
<entry > Instance name</entry>
2013-06-30 00:09:14 +08:00
<entry > For instantiated units: this is the string between the <literal > @</literal> character and the suffix.</entry>
2013-01-11 07:21:06 +08:00
</row>
<row >
<entry > <literal > %I</literal> </entry>
<entry > Unescaped instance name</entry>
<entry > </entry>
</row>
<row >
<entry > <literal > %f</literal> </entry>
2013-06-28 03:51:44 +08:00
<entry > Unescaped filename</entry>
2013-04-30 07:55:34 +08:00
<entry > This is either the unescaped instance name (if applicable) with <filename > /</filename> prepended (if applicable), or the prefix name similarly prepended with <filename > /</filename> .</entry>
2013-01-11 07:21:06 +08:00
</row>
<row >
<entry > <literal > %c</literal> </entry>
<entry > Control group path of the unit</entry>
<entry > </entry>
</row>
<row >
<entry > <literal > %r</literal> </entry>
2013-04-30 07:55:34 +08:00
<entry > Root control group path where units are placed.</entry>
<entry > For system instances this usually resolves to <filename > /system</filename> , except in containers, where the path might be prefixed with the container's root control group.</entry>
2013-01-11 07:21:06 +08:00
</row>
<row >
<entry > <literal > %R</literal> </entry>
2013-04-30 07:55:34 +08:00
<entry > Parent directory of the control group path where units are placed.</entry>
<entry > For system instances this usually resolves to <filename > /</filename> , except in containers, where this resolves to the container's root directory. This specifier is particularly useful in the <varname > ControlGroup=</varname> setting (see <citerefentry > <refentrytitle > systemd.exec</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ).</entry>
2013-01-11 07:21:06 +08:00
</row>
<row >
<entry > <literal > %t</literal> </entry>
<entry > Runtime socket dir</entry>
<entry > This is either <filename > /run</filename> (for the system manager) or <literal > $XDG_RUNTIME_DIR</literal> (for user managers).</entry>
</row>
<row >
<entry > <literal > %u</literal> </entry>
<entry > User name</entry>
<entry > This is the name of the configured user of the unit, or (if none is set) the user running the systemd instance.</entry>
</row>
<row >
<entry > <literal > %U</literal> </entry>
<entry > User UID</entry>
<entry > This is the UID of the configured user of the unit, or (if none is set) the user running the systemd instance.</entry>
</row>
<row >
<entry > <literal > %h</literal> </entry>
<entry > User home directory</entry>
<entry > This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd instance.</entry>
</row>
<row >
<entry > <literal > %s</literal> </entry>
<entry > User shell</entry>
2013-04-30 07:55:34 +08:00
<entry > This is the shell of the configured user of the unit, or (if none is set) the user running the systemd instance. If the user is <literal > root</literal> (UID equal to 0), the shell configured in account database is ignored and <filename > /bin/sh</filename> is always used.</entry>
2013-01-11 07:21:06 +08:00
</row>
<row >
<entry > <literal > %m</literal> </entry>
<entry > Machine ID</entry>
<entry > The machine ID of the running system, formatted as string. See <citerefentry > <refentrytitle > machine-id</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for more information.</entry>
</row>
<row >
<entry > <literal > %b</literal> </entry>
<entry > Boot ID</entry>
<entry > The boot ID of the running system, formatted as string. See <citerefentry > <refentrytitle > random</refentrytitle> <manvolnum > 4</manvolnum> </citerefentry> for more information.</entry>
</row>
<row >
<entry > <literal > %H</literal> </entry>
<entry > Host name</entry>
2013-06-28 03:51:44 +08:00
<entry > The hostname of the running system.</entry>
2013-01-11 07:21:06 +08:00
</row>
2013-07-19 14:45:27 +08:00
<row >
<entry > <literal > %v</literal> </entry>
<entry > Kernel release</entry>
<entry > Identical to <command > uname -r</command> output.</entry>
</row>
2013-02-20 18:17:43 +08:00
<row >
<entry > <literal > %%</literal> </entry>
<entry > Escaped %</entry>
<entry > Single percent sign.</entry>
</row>
2013-01-11 07:21:06 +08:00
</tbody>
</tgroup>
</table>
</refsect1>
2010-05-16 05:06:41 +08:00
<refsect1 >
2010-06-24 06:11:04 +08:00
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2010-06-24 23:22:52 +08:00
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.special</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.service</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.socket</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.device</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.mount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.automount</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.swap</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.target</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.path</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2010-07-02 23:23:19 +08:00
<citerefentry > <refentrytitle > systemd.timer</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2011-10-11 21:16:52 +08:00
<citerefentry > <refentrytitle > systemd.snapshot</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2013-07-24 23:31:17 +08:00
<citerefentry > <refentrytitle > systemd.scope</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.slice</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
2012-11-24 07:24:14 +08:00
<citerefentry > <refentrytitle > systemd.time</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
2013-01-15 11:08:33 +08:00
<citerefentry > <refentrytitle > capabilities</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
2013-07-19 14:45:27 +08:00
<citerefentry > <refentrytitle > systemd.directives</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > uname</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2010-06-24 06:11:04 +08:00
</para>
2010-05-16 05:06:41 +08:00
</refsect1>
</refentry>
