X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.unit.xml;h=00f60667175db2c63938cf05ab0fe6e31e70c249;hb=742a862bb803641b78a40f6b498486397a321294;hp=bdd8f7d7014cd67010969b9a9ce3de97ba399b55;hpb=85e9a1010d16064ce435b84f02dc585bc645aade;p=elogind.git
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index bdd8f7d70..00f606671 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -363,7 +363,15 @@
Requires= in order
to achieve a system that is more
robust when dealing with failing
- services.
+ services.
+
+ Note that dependencies of this
+ type may also be configured outside of
+ the unit configuration file by
+ adding a symlink to a
+ .requires/ directory
+ accompanying the unit file. For
+ details see above.
@@ -415,7 +423,9 @@
the transaction as a whole. This is
the recommended way to hook start-up
of one unit to the start-up of another
- unit. Note that dependencies of this
+ unit.
+
+ Note that dependencies of this
type may also be configured outside of
the unit configuration file by
adding a symlink to a
@@ -444,16 +454,16 @@
PartOf=
- Configures dependency
- on other unit. When systemd stops or
- restarts unit listed here, stop or
- restart is propagated to dependent
- units. Note that this is one way
- dependency and changes to dependent
- units does not affect listed unit. If
- something else is desired, please
- use some other type of dependency.
-
+ Configures dependencies
+ similar to Requires=,
+ 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.
+
@@ -576,7 +586,7 @@
RequiresMountsFor=
Takes a space
- separated list of paths. Automatically
+ separated list of absolute paths. Automatically
adds dependencies of type
Requires= and
After= for all
@@ -745,70 +755,99 @@
ConditionPathIsMountPoint=
ConditionPathIsReadWrite=
ConditionDirectoryNotEmpty=
+ ConditionFileNotEmpty=
ConditionFileIsExecutable=
ConditionKernelCommandLine=
ConditionVirtualization=
ConditionSecurity=
ConditionCapability=
+ ConditionHost=
ConditionNull=
Before starting a unit
verify that the specified condition is
- true. With
+ 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.
+
+ With
ConditionPathExists=
- a file existence condition can be
+ a file existence condition is
checked before a unit is started. If
the specified absolute path name does
- not exist, startup of a unit will not
- actually happen, however the unit is
- still useful for ordering purposes in
- this case. The condition is checked at
- the time the queued start job is to be
- executed. If the absolute path name
- passed to
+ not exist the condition will
+ fail. If the absolute path name passed
+ to
ConditionPathExists=
is prefixed with an exclamation mark
- (!), the test is negated, and the unit
+ ('!'), the test is negated, and the unit
is only started if the path does not
- exist.
- ConditionPathExistsGlob=
- works in a similar way, but checks for
- the existence of at least one file or
- directory matching the specified
- globbing
- pattern. ConditionPathIsDirectory=
+ exist.
+
+ ConditionPathExistsGlob=
+ is similar to
+ ConditionPathExists=,
+ but checks for the existence of at
+ least one file or directory matching
+ the specified globbing pattern.
+
+ ConditionPathIsDirectory=
is similar to
ConditionPathExists=
but verifies whether a certain path
exists and is a
- directory. ConditionPathIsSymbolicLink=
+ directory.
+
+ ConditionPathIsSymbolicLink=
is similar to
ConditionPathExists=
but verifies whether a certain path
exists and is a symbolic
- link. ConditionPathIsMountPoint=
+ link.
+
+ ConditionPathIsMountPoint=
is similar to
ConditionPathExists=
but verifies whether a certain path
exists and is a mount
- point. ConditionPathIsReadWrite=
+ point.
+
+ ConditionPathIsReadWrite=
is similar to
ConditionPathExists=
but verifies whether the underlying
- file system is read and writable
+ file system is readable and writable
(i.e. not mounted
- read-only). ConditionFileIsExecutable=
+ read-only).
+
+ ConditionDirectoryNotEmpty=
is similar to
ConditionPathExists=
but verifies whether a certain path
- exists, is a regular file and marked
- executable.
- ConditionDirectoryNotEmpty=
+ exists and is a non-empty
+ directory.
+
+ ConditionFileNotEmpty=
is similar to
ConditionPathExists=
but verifies whether a certain path
- exists and is a non-empty
- directory. Similarly
+ exists and refers to a regular file
+ with a non-zero size.
+
+ ConditionFileIsExecutable=
+ is similar to
+ ConditionPathExists=
+ but verifies whether a certain path
+ exists, is a regular file and marked
+ executable.
+
+ Similar,
ConditionKernelCommandLine=
may be used to check whether a
specific kernel command line option is
@@ -816,14 +855,16 @@
exclamation mark unset). The argument
must either be a single word, or an
assignment (i.e. two words, separated
- by the equality sign). In the former
+ '='). In the former
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
- matching. ConditionVirtualization=
+ matching.
+
+ ConditionVirtualization=
may be used to check whether the
system is executed in a virtualized
environment and optionally test
@@ -833,7 +874,7 @@
any virtualized environment, or one of
vm and
container to test
- against a specific type of
+ against a generic type of
virtualization solution, or one of
qemu,
kvm,
@@ -852,15 +893,18 @@
virtualization technologies are nested
only the innermost is considered. The
test may be negated by prepending an
- exclamation mark.
- ConditionSecurity=
+ exclamation mark.
+
+ ConditionSecurity=
may be used to check whether the given
security module is enabled on the
system. Currently the only recognized
value is selinux.
The test may be negated by prepending
an exclamation
- mark. ConditionCapability=
+ mark.
+
+ ConditionCapability=
may be used to check whether the given
capability exists in the capability
bounding set of the service manager
@@ -871,14 +915,32 @@
for details). Pass a capability name
such as CAP_MKNOD,
possibly prefixed with an exclamation
- mark to negate the check. Finally,
+ mark to negate the check.
+
+ ConditionHost=
+ may be used to match against the
+ host name or machine ID of the
+ host. This either takes a host name
+ string (optionally with shell style
+ globs) which is tested against the
+ locally set host name as returned by
+ gethostname2,
+ or a machine ID formatted as string
+ (see
+ machine-id5).
+ The test may be negated by prepending
+ an exclamation mark.
+
+ Finally,
ConditionNull= may
be used to add a constant condition
check value to the unit. It takes a
boolean argument. If set to
false the condition
will always fail, otherwise
- succeed. If multiple conditions are
+ succeed.
+
+ If multiple conditions are
specified the unit will be executed if
all of them apply (i.e. a logical AND
is applied). Condition checks can be