From: Zbigniew Jędrzejewski-Szmek Date: Mon, 16 Apr 2018 15:42:10 +0000 (+0200) Subject: man: briefly document Following= X-Git-Tag: v239~397^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2116134b04abbe34afbb2269f59b1c3610c7794a;p=platform%2Fupstream%2Fsystemd.git man: briefly document Following= Fixes #1914. --- diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 5ea615d..8b4a294 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1312,7 +1312,7 @@ Unit settings that create a relationship with a second unit usually show up in properties of both units, for example in systemctl show 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. @@ -1387,6 +1387,11 @@ ReloadPropagatedFrom= PropagatesReloadTo= + + Following= + n/a + An automatic property + @@ -1412,6 +1417,10 @@ systemd.automount5 for details. TriggersBy= is created implicitly on the triggered unit. + + Note: Following= 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.