... | @@ -83,8 +83,8 @@ The 7s-sleeper and the 9s-sleeper went from alive to |
... | @@ -83,8 +83,8 @@ The 7s-sleeper and the 9s-sleeper went from alive to |
|
not-alive in different ways here: the former exited while
|
|
not-alive in different ways here: the former exited while
|
|
the latter was terminated, e.g. by having a signal sent to
|
|
the latter was terminated, e.g. by having a signal sent to
|
|
it. This distinction can be relevant. That's why `wait-process`
|
|
it. This distinction can be relevant. That's why `wait-process`
|
|
exposes it whenever possible: If a process is killed by signal
|
|
exposes it whenever possible: If a process is terminated by signal
|
|
15, its return code will be 128+15=143. To distinguish that
|
|
15 (SIGTERM), its return code will be 128+15=143. To distinguish that
|
|
from a regular exit with return code 143,
|
|
from a regular exit with return code 143,
|
|
`wait-process` will return the two values 143 and 15 whenever possible.
|
|
`wait-process` will return the two values 143 and 15 whenever possible.
|
|
A clean exit with return code 0 can still always simply be checked for
|
|
A clean exit with return code 0 can still always simply be checked for
|
... | | ... | |