diff options
| author | Richard Maw <richard.maw@codethink.co.uk> | 2015-08-11 12:29:45 +0000 |
|---|---|---|
| committer | Richard Maw <richard.maw@codethink.co.uk> | 2015-08-11 13:01:53 +0000 |
| commit | 12e2683d4804326d29ebf92bba9f0dd3810a5ead (patch) | |
| tree | b2cc69318687ab40d4915b68489fd79fcbb6a54e /test/sched_rr_ok.service | |
| parent | 3f1818cf70ac34cf93f1f033b4f1bbb7a89b3dff (diff) | |
man: Describe when ExecStartFoo= commands are run in more detail
Previously it was just descibed that ExecStartPost= commands were
started "after" the ExecStart= command(s).
This hasn't specified after which event, which varies from after it has
been started, after it has exited, after it has sent READY=1 or after it
has taken the bus name, depending on Type=.
This now describes that it happens after the *service* has "started",
as defined by the Type=, and provides some clarification about precisely
when this is.
This may be unnecessary duplication, but it removes the ambiguity as to
whether RemainAfterExit=no means that ExecStartPost= shouldn't be
started because it means the service has stopped when the ExecStart=
command terminates, not "started".
Diffstat (limited to 'test/sched_rr_ok.service')
0 files changed, 0 insertions, 0 deletions