diff options
| author | Lennart Poettering <lennart@poettering.net> | 2010-10-28 23:18:47 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2010-10-29 00:45:46 +0200 |
| commit | b81884e7466b8e8bc1261b1b1a722d11694b8c54 (patch) | |
| tree | a974af7656baa8eadb0bb0fec0bfe44e4885bb8c /man/systemd.unit.xml | |
| parent | 941a4041bdb9d91e9d5033005263efe029621e4f (diff) | |
unit: replace StopRetroactively= by BindTo= dependencies
The property StopRetroactively= needs to be per-dependency, not
per-unit, in order to properly express dependencies between .mount units
and its .device and fsck .service units. If the .device unit is
unplugged the mount should go away, but if the fsck process terminates
the .mount should stay.
Diffstat (limited to 'man/systemd.unit.xml')
| -rw-r--r-- | man/systemd.unit.xml | 42 |
1 files changed, 18 insertions, 24 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 14da607a95..ff1b47f9fb 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -281,7 +281,6 @@ services.</para></listitem> </varlistentry> - <varlistentry> <term><varname>RequiresOverridable=</varname></term> @@ -341,6 +340,23 @@ </varlistentry> <varlistentry> + <term><varname>BindTo=</varname></term> + + <listitem><para>Configures requirement + dependencies, very similar in style to + <varname>Requires=</varname>, 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 with involvement of + systemd.</para></listitem> + </varlistentry> + + <varlistentry> <term><varname>Conflicts=</varname></term> <listitem><para>Configures negative @@ -441,28 +457,6 @@ </varlistentry> <varlistentry> - <term><varname>StopRetroactively=</varname></term> - - <listitem><para>Takes a boolean - argument. If <option>true</option> and - a unit this unit requires stops - without this being requested by the - user, this unit will be stopped as - well. (e.g. if a service exits or - crashes on its own behalf, units this - flag is set for that require 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 - <option>false</option>.</para></listitem> - </varlistentry> - - <varlistentry> <term><varname>StopWhenUnneeded=</varname></term> <listitem><para>Takes a boolean @@ -630,7 +624,7 @@ 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 + applies (i.e. a logical OR is applied).</para></listitem> </varlistentry> </variablelist> |