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
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
name contains an <literal>@</literal> character, systemd will look for a
unit template that shares the same name but with the
instance string (i.e. the part between the <literal>@</literal> character
name contains an <literal>@</literal> character, systemd will look for a
unit template that shares the same name but with the
instance string (i.e. the part between the <literal>@</literal> character
what the unit's purpose is, followed
by how it is configured, followed by
any other related documentation. This
what the unit's purpose is, followed
by how it is configured, followed by
any other related documentation. This
in which case the specified list of
URIs is merged. If the empty string is
assigned to this option, the list is
in which case the specified list of
URIs is merged. If the empty string is
assigned to this option, the list is
<varname>Requires=</varname> and
<varname>RequiresOverridable=</varname>,
respectively. However, if the units
<varname>Requires=</varname> and
<varname>RequiresOverridable=</varname>,
respectively. However, if the units
listed in this option will be started
if the configuring unit is. However,
if the listed units fail to start
listed in this option will be started
if the configuring unit is. However,
if the listed units fail to start
this has no impact on the validity of
the transaction as a whole. This is
the recommended way to hook start-up
this has no impact on the validity of
the transaction as a whole. This is
the recommended way to hook start-up
<listitem><para>Configures requirement
dependencies, very similar in style to
<varname>Requires=</varname>, however
<listitem><para>Configures requirement
dependencies, very similar in style to
<varname>Requires=</varname>, however
declares that this unit is stopped
when any of the units listed suddenly
disappears. Units can suddenly,
declares that this unit is stopped
when any of the units listed suddenly
disappears. Units can suddenly,
of units. When systemd stops or restarts
the units listed here, the action is
propagated to this unit.
of units. When systemd stops or restarts
the units listed here, the action is
propagated to this unit.
be modified to be fixed (in case one
or both jobs are not a required part
of the transaction). In the latter
be modified to be fixed (in case one
or both jobs are not a required part
of the transaction). In the latter
which case the unit listed will be
started before the unit that is
configured with these options. This
which case the unit listed will be
started before the unit that is
configured with these options. This
dependency on another unit is shut
down while the latter is started up,
the shut down is ordered before the
dependency on another unit is shut
down while the latter is started up,
the shut down is ordered before the
ordering dependency is actually of
type <varname>After=</varname> or
<varname>Before=</varname>. If two
ordering dependency is actually of
type <varname>After=</varname> or
<varname>Before=</varname>. If two
directives (see
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details). If a unit that has this
directives (see
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details). If a unit that has this
will see the same
<filename>/tmp</filename>,
<filename>/tmp/var</filename> and
network namespace as one listed unit
that is started. If multiple listed
will see the same
<filename>/tmp</filename>,
<filename>/tmp/var</filename> and
network namespace as one listed unit
that is started. If multiple listed
<varname>ConditionKernelCommandLine=</varname>
may be used to check whether a
specific kernel command line option is
<varname>ConditionKernelCommandLine=</varname>
may be used to check whether a
specific kernel command line option is
- <entry>For instantiated units this refers to the string before the <literal>@</literal> character of the unit name. For non-instantiated units this refers to the name of the unit with the type suffix removed.</entry>
+ <entry>For instantiated units, this refers to the string before the <literal>@</literal> character of the unit name. For non-instantiated units, this refers to the name of the unit with the type suffix removed.</entry>
<entry>For system instances, this resolves to <filename>/</filename>, except in containers, where this maps to the container's root control group path.</entry>
</row>
<row>
<entry>For system instances, this resolves to <filename>/</filename>, except in containers, where this maps to the container's root control group path.</entry>
</row>
<row>
- <entry>This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal> this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
+ <entry>This is the home directory of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal>, this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
- <entry>This is the shell of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal> this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>
+ <entry>This is the shell of the configured user of the unit, or (if none is set) the user running the systemd user instance. Similar to <literal>%U</literal>, this specifier is not available for units run by the systemd system instance, unless the configured user is the root user.</entry>