configuration options. Other specifiers that may be
used are <literal>%n</literal>, <literal>%N</literal>,
<literal>%p</literal>, <literal>%P</literal>,
- <literal>%I</literal> and <literal>%f</literal>, for
+ <literal>%I</literal>, <literal>%f</literal>,
+ <literal>%c</literal>, <literal>%r</literal>,
+ <literal>%R</literal> and <literal>%t</literal> for
the full unit name, the unescaped unit name, the
prefix name, the unescaped prefix name, the unescaped
- instance name and the unescaped filename,
+ instance name, the unescaped filename, the control
+ group path of the unit, the root control group path of
+ systemd, and the parent directory of the root control
+ cgroup path of systemd and the runtime socket dir,
respectively. The unescaped filename is either the
unescaped instance name (if set) with / prepended (if
necessary), or the prefix name similarly prepended
with /. The prefix name here refers to the string
before the @, i.e. "getty" in the example above, where
- "tty3" is the instance name.</para>
+ "tty3" is the instance name. The runtime socket
+ directory is either <filename>/run</filename> (for the
+ system manager) or <literal>$XDG_RUNTIME_DIR</literal>
+ (for user managers).</para>
<para>If a unit file is empty (i.e. has the file size
0) or is symlinked to <filename>/dev/null</filename>
argument. If <option>true</option>
this unit will not be included in
snapshots. Defaults to
- <option>false</option> for device and
- snapshot units, <option>true</option>
+ <option>true</option> for device and
+ snapshot units, <option>false</option>
for the others.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>ConditionPathExists=</varname></term>
+ <term><varname>ConditionPathExistsGlob=</varname></term>
<term><varname>ConditionPathIsDirectory=</varname></term>
<term><varname>ConditionDirectoryNotEmpty=</varname></term>
+ <term><varname>ConditionFileIsExecutable=</varname></term>
<term><varname>ConditionKernelCommandLine=</varname></term>
<term><varname>ConditionVirtualization=</varname></term>
<term><varname>ConditionSecurity=</varname></term>
is prefixed with an exclamation mark
(!), the test is negated, and the unit
only started if the path does not
- exist. <varname>ConditionPathIsDirectory=</varname>
+ exist. <varname>ConditionPathExistsGlob=</varname>
+ work in a similar way, but checks for
+ the existance of at least one file or
+ directory matching the specified
+ globbing
+ pattern. <varname>ConditionPathIsDirectory=</varname>
is similar to
<varname>ConditionPathExists=</varname>
but verifies whether a certain path
- exists and is a directory.
+ exists and is a
+ directory. <varname>ConditionFileIsExecutable=</varname>
+ is similar to
+ <varname>ConditionPathExists=</varname>
+ but verifies whether a certain path
+ exists, is a regular file and marked
+ executable.
<varname>ConditionDirectoryNotEmpty=</varname>
is similar to
<varname>ConditionPathExists=</varname>
test may be negated by prepending an
exclamation mark.
<varname>ConditionSecurity=</varname>
- may be used to check whether the given security
- module is enabled on the system.
- Currently the only recognized value is
- <varname>selinux</varname>.
- The test may be negated by prepending an
- exclamation mark. Finally,
+ may be used to check whether the given
+ security module is enabled on the
+ system. Currently the only recognized
+ value is <varname>selinux</varname>.
+ The test may be negated by prepending
+ an exclamation mark. Finally,
<varname>ConditionNull=</varname> may
be used to add a constant condition
check value to the unit. It takes a
~ianmdlvl / elogind.git / blobdiff