X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.unit.xml;h=fa8821afe5a7c94b19578666511841f88dd4ec45;hb=7fc7012b8b54bdd6610d32649d4ee9c938a4843d;hp=f72b947dca052ffefc7fe99d0eb344638a9b829d;hpb=9fc507041eb524799a0410839e961ec188a78491;p=elogind.git
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index f72b947dc..fa8821afe 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -281,7 +281,6 @@
services.
-
RequiresOverridable=
@@ -340,6 +339,23 @@
details see above.
+
+ BindTo=
+
+ Configures requirement
+ dependencies, very similar in style to
+ Requires=, however
+ in addition to this behaviour it also
+ 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
+ unmounted without involvement of
+ systemd.
+
+
Conflicts=
@@ -440,26 +456,6 @@
state.
-
- RecursiveStop=
-
- Takes a boolean
- argument. If and
- the unit stops without being requested
- by the user, all units
- depending on it will be stopped as
- well. (e.g. if a service exits or
- crashes on its own behalf, units using
- it will be stopped) Note that normally
- if a unit stops without a user request,
- units depending on it will not be
- terminated. Only if the user requested
- shutdown of a unit, all units depending
- on that unit will be shut down as well
- and at the same time. Defaults to
- .
-
-
StopWhenUnneeded=
@@ -547,20 +543,6 @@
ones.
-
- IgnoreDependencyFailure=
-
- Takes a boolean
- argument. If and
- a requirement dependency of this unit
- fails to start up this unit will be
- started nonetheless, ignoring that
- failure. If
- (the default) and a dependency unit
- fails the unit will immediately fail
- too and the job is removed.
-
-
JobTimeoutSec=
@@ -591,7 +573,10 @@
ConditionPathExists=
+ ConditionDirectoryNotEmpty=ConditionKernelCommandLine=
+ ConditionVirtualization=
+ ConditionNull=Before starting a unit
verify that the specified condition is
@@ -611,24 +596,54 @@
is prefixed with an exclamation mark
(!), the test is negated, and the unit
only started if the path does not
- exist. Similarly
+ exist. ConditionDirectoryNotEmpty=
+ is similar to
+ ConditionPathExists=
+ but verifies whether a certain path is
+ exists and is a non-empty
+ directory. Similarly
ConditionKernelCommandLine=
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
- assignment (i.e. two words, seperated
+ assignment (i.e. two words, separated
by the equality sign). In the former
- case the kernel command line is search
- 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. If multiple conditions
- are specified the unit will be
- executed iff at least one of them
- apply (i.e. a logical OR is
+ 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=
+ 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
+ value to check if being executed in any
+ virtual environment or one of the
+ qemu,
+ kvm,
+ vmware,
+ microsoft,
+ oracle,
+ xen,
+ openvz to test
+ against a specific implementation. 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
+ specified the unit will be executed if
+ at least one of them applies (i.e. a
+ logical OR is
applied).