summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2017-10-04 21:43:00 +0900
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2017-10-04 14:43:00 +0200
commit6b5bb2f9d03ec016952c8193a8a63304beac993f (patch)
tree453e46b0e8af44c0d01e08c3664285d04ef20c0e
parent0a9b166b43e9d035034beb929ed2c892094af9dc (diff)
downloadsystemd-6b5bb2f9d03ec016952c8193a8a63304beac993f.tar.gz
man: fix that the same option is listed twice (#6991)
-rw-r--r--man/systemd.unit.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index be65cc3c85..bec6356270 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -469,7 +469,7 @@
<para>Note that this dependency type does not imply that the other unit always has to be in active state when
this unit is running. Specifically: failing condition checks (such as <varname>ConditionPathExists=</varname>,
- <varname>ConditionPathExists=</varname>, … — see below) do not cause the start job of a unit with a
+ <varname>ConditionPathIsSymbolicLink=</varname>, … — see below) do not cause the start job of a unit with a
<varname>Requires=</varname> dependency on it to fail. Also, some unit types may deactivate on their own (for
example, a service process may decide to exit cleanly, or a device may be unplugged by the user), which is not
propagated to units having a <varname>Requires=</varname> dependency. Use the <varname>BindsTo=</varname>