diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2017-03-29 14:37:47 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2017-03-29 14:37:47 +0000 |
| commit | d8ed499d05f38a8097289e3ee1aeeb3cd7c615a0 (patch) | |
| tree | 516f059fda8f320bf3e975cb25a56de346f8475f | |
| parent | 776e5e27136fdb49bd4709d0d6adce7a15985fa9 (diff) | |
| download | s6-d8ed499d05f38a8097289e3ee1aeeb3cd7c615a0.tar.xz | |
s6-svstat doc typo fix and clarification
| -rw-r--r-- | doc/s6-svstat.html | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/s6-svstat.html b/doc/s6-svstat.html index afa6d39..2a88feb 100644 --- a/doc/s6-svstat.html +++ b/doc/s6-svstat.html @@ -85,13 +85,14 @@ if it is not (i.e. there is a <tt>./down</tt> file). </li> it is not. Note that a service can be both <em>down</em> and <em>ready</em>: it simply means that it is ready to be started (i.e. no <tt>./finish</tt> script is currently running). To check for service readiness, you should give this option along with <tt>up</tt>: the service is ready iff -<tt>s6-svstat -o up,ready</tt> prints <tt>true true</tt>. </li> +<tt>s6-svstat -o up,ready</tt> prints <tt>true true</tt>. (The <tt>true true</tt> case will +never happen if the service does not support readiness notification.) </li> <li> <tt>paused</tt>: print <tt>true</tt> if the service is paused (i.e. the process is currently stopped) and <tt>false</tt> if it is not. It is a rare flag, you shouldn't normally need to use this option. </li> <li> <tt>pid</tt>: print the pid of the supervised process. If the service is currently down, <tt>-1</tt> is printed instead. </li> - <li> <tt>pid</tt>: print the exit code of the last execution of <tt>./run</tt>. If the + <li> <tt>exitcode</tt>: print the exit code of the last execution of <tt>./run</tt>. If the service is currently up, or the last <tt>./run</tt> process was killed by a signal, <tt>-1</tt> is printed instead. </li> <li> <tt>signal</tt>: print the name of the signal the last <tt>./run</tt> process was |