diff options
| author | Ian Kelling <ian@iankelling.org> | 2016-02-21 18:21:50 -0800 |
|---|---|---|
| committer | Ian Kelling <ian@iankelling.org> | 2016-02-23 21:30:39 -0800 |
| commit | 21b0be6bcfee857a8c88d21c9f876955229be873 (patch) | |
| tree | d4072078cfb89ee526eeb47fcf78dd8c47d991aa | |
| parent | 1f210bdbe65dffcb6daeb9d9cddbf0b2d02f8718 (diff) | |
man: clarify unit ordering language
| -rw-r--r-- | man/systemd.unit.xml | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 5794681963..f5022b03cc 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -558,14 +558,17 @@ between them are shut down, the inverse of the start-up order is applied. i.e. if a unit is configured with <varname>After=</varname> on another unit, the former is - stopped before the latter if both are shut down. If one unit - with an ordering dependency on another unit is shut down while - the latter is started up, the shut down is ordered before the - start-up regardless of whether the ordering dependency is - actually of type <varname>After=</varname> or - <varname>Before=</varname>. If two units have no ordering - dependencies between them, they are shut down or started up - simultaneously, and no ordering takes place. + stopped before the latter if both are shut down. Given two units + with any ordering dependency between them, if one unit is shut + down and the other is started up, the shutdown is ordered + before the start-up. It doesn't matter if the ordering + dependency is <varname>After=</varname> or + <varname>Before=</varname>. It also doesn't matter which of the + two is shut down, as long as one is shut down and the other is + started up. The shutdown is ordered before the start-up in all + cases. If two units have no ordering dependencies between them, + they are shut down or started up simultaneously, and no ordering + takes place. </para></listitem> </varlistentry> |