X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=man%2Fsystemd.unit.xml;h=5460ebeb2f1923755cbcfd2b625cce11d9c56178;hb=9d8677dad260d7dc20146f8affe3d376daff7c19;hp=fa8821afe5a7c94b19578666511841f88dd4ec45;hpb=039655a40c77f88e4f9ccc00824f2f483f22f2c1;p=elogind.git
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index fa8821afe..5460ebeb2 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -139,7 +139,10 @@
with the enable command of the
systemctl1
tool which reads information from the [Install]
- section of unit files. (See below.)
+ section of unit files. (See below.) A similar
+ functionality exists for Requires=
+ type dependencies as well, the directory suffix is
+ .requires/ in this case.
Note that while systemd offers a flexible
dependency system between units it is recommended to
@@ -216,21 +219,6 @@
dependent on the type of unit:
-
- Names=
-
- Additional names for
- this unit. 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. Note
- that this option is different from the
- Alias= option from
- the [Install] section mentioned
- below. See below for details.
-
-
Description=
@@ -573,9 +561,11 @@
ConditionPathExists=
+ ConditionPathIsDirectory=
ConditionDirectoryNotEmpty=
ConditionKernelCommandLine=
ConditionVirtualization=
+ ConditionSecurity=
ConditionNull=
Before starting a unit
@@ -596,10 +586,15 @@
is prefixed with an exclamation mark
(!), the test is negated, and the unit
only started if the path does not
- exist. ConditionDirectoryNotEmpty=
+ exist. ConditionPathIsDirectory=
+ is similar to
+ ConditionPathExists=
+ but verifies whether a certain path
+ exists and is a directory.
+ ConditionDirectoryNotEmpty=
is similar to
ConditionPathExists=
- but verifies whether a certain path is
+ but verifies whether a certain path
exists and is a non-empty
directory. Similarly
ConditionKernelCommandLine=
@@ -622,17 +617,25 @@
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
+ value to check if being executed in
+ any virtual environment or one of the
qemu,
kvm,
vmware,
microsoft,
oracle,
xen,
+ pidns,
openvz to test
against a specific implementation. The
test may be negated by prepending an
+ 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. Finally,
ConditionNull= may
be used to add a constant condition
@@ -642,9 +645,49 @@
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).
+ 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
+ exclamation second.
+
+
+
+ Names=
+
+ Additional names for
+ this unit. 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. Note
+ that this option is different from the
+ Alias= option from
+ the [Install] section mentioned
+ below. See below for details. Note
+ that in almost all cases this option
+ is not what you want. A symlink alias
+ in the file system is generally
+ preferable since it can be used as
+ lookup key. If a unit with a symlinked
+ alias name is not loaded and needs to
+ be it is easily found via the
+ symlink. However, if a unit with an
+ alias name configured with this
+ setting is not loaded it will not be
+ discovered. This settings' only use is
+ in conjunction with service
+ instances.
+