summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2018-04-16 17:42:10 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2018-04-18 09:16:17 +0200
commit2116134b04abbe34afbb2269f59b1c3610c7794a (patch)
tree54b8780328b26bb11e009ec9fdaf9eeeb03912c4 /man
parent492cb5095b0b742339bb9356ea9ef347843ef238 (diff)
downloadsystemd-2116134b04abbe34afbb2269f59b1c3610c7794a.tar.gz
systemd-2116134b04abbe34afbb2269f59b1c3610c7794a.tar.bz2
systemd-2116134b04abbe34afbb2269f59b1c3610c7794a.zip
man: briefly document Following=
Fixes #1914.
Diffstat (limited to 'man')
-rw-r--r--man/systemd.unit.xml11
1 files changed, 10 insertions, 1 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index 5ea615d998..8b4a29445d 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -1312,7 +1312,7 @@
<para>Unit settings that create a relationship with a second unit usually show up
in properties of both units, for example in <command>systemctl show</command>
output. In some cases the name of the property is the same as the name of the
- configuration setting, but not always. This table lists the pairs of properties
+ configuration setting, but not always. This table lists the properties
that are shown on two units which are connected through some dependency, and shows
which property on "source" unit corresponds to which property on the "target" unit.
</para>
@@ -1387,6 +1387,11 @@
<entry><varname>ReloadPropagatedFrom=</varname></entry>
<entry><varname>PropagatesReloadTo=</varname></entry>
</row>
+ <row>
+ <entry><varname>Following=</varname></entry>
+ <entry>n/a</entry>
+ <entry>An automatic property</entry>
+ </row>
</tbody>
</tgroup>
</table>
@@ -1412,6 +1417,10 @@
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details. <varname>TriggersBy=</varname> is created implicitly on the
triggered unit.</para>
+
+ <para>Note: <varname>Following=</varname> is used to group device aliases and points to the
+ "primary" device unit that systemd is using to track device state, usually corresponding to a
+ sysfs path. It does not show up in the "target" unit.</para>
</refsect1>
<refsect1>