mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-12-22 13:33:56 +03:00
man: add "timeout" to status table (#3919)
This commit is contained in:
parent
6998b54093
commit
29df65f913
@ -1668,6 +1668,18 @@
|
||||
</thead>
|
||||
|
||||
<tbody>
|
||||
<row>
|
||||
<entry morerows="1" valign="top"><literal>timeout</literal></entry>
|
||||
<entry valign="top"><literal>killed</literal></entry>
|
||||
<entry><literal>TERM</literal><sbr/><literal>KILL</literal></entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry valign="top"><literal>exited</literal></entry>
|
||||
<entry><literal>0</literal><sbr/><literal>1</literal><sbr/><literal>2</literal><sbr/><literal
|
||||
>3</literal><sbr/>…<sbr/><literal>255</literal></entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry valign="top"><literal>exit-code</literal></entry>
|
||||
<entry valign="top"><literal>exited</literal></entry>
|
||||
@ -1707,6 +1719,10 @@
|
||||
<entry>any of the above</entry>
|
||||
<entry>any of the above</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry namest="results" nameend="code">Note: the process may be also terminated by a signal not sent by systemd. In particular the process may send an arbitrary signal to itself in a handler for any of the non-maskable signals. Nevertheless, in the <literal>timeout</literal> and <literal>watchdog</literal> rows above only the signals that systemd sends have been included.</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
@ -276,17 +276,12 @@
|
||||
below (see section "Command Lines" below).
|
||||
</para>
|
||||
|
||||
<para>When <varname>Type=</varname> is not
|
||||
<option>oneshot</option>, only one command may and must be
|
||||
given. When <varname>Type=oneshot</varname> is used, zero or
|
||||
more commands may be specified. This can be specified by
|
||||
providing multiple command lines in the same directive, or
|
||||
alternatively, this directive may be specified more than once
|
||||
with the same effect. If the empty string is assigned to this
|
||||
option, the list of commands to start is reset, prior
|
||||
assignments of this option will have no effect. If no
|
||||
<varname>ExecStart=</varname> is specified, then the service
|
||||
must have <varname>RemainAfterExit=yes</varname> set.</para>
|
||||
<para>Unless <varname>Type=</varname> is <option>oneshot</option>, exactly one command must be given. When
|
||||
<varname>Type=oneshot</varname> is used, zero or more commands may be specified. Commands may be specified by
|
||||
providing multiple command lines in the same directive, or alternatively, this directive may be specified more
|
||||
than once with the same effect. If the empty string is assigned to this option, the list of commands to start
|
||||
is reset, prior assignments of this option will have no effect. If no <varname>ExecStart=</varname> is
|
||||
specified, then the service must have <varname>RemainAfterExit=yes</varname> set.</para>
|
||||
|
||||
<para>For each of the specified commands, the first argument must be an absolute path to an
|
||||
executable. Optionally, if this file name is prefixed with <literal>@</literal>, the second token will be
|
||||
@ -294,7 +289,7 @@
|
||||
the absolute filename is prefixed with <literal>-</literal>, an exit code of the command normally considered a
|
||||
failure (i.e. non-zero exit status or abnormal exit due to signal) is ignored and considered success. If the
|
||||
absolute path is prefixed with <literal>+</literal> then it is executed with full
|
||||
privileges. <literal>-</literal>, <literal>@</literal>, and <literal>+</literal> may be used together and they
|
||||
privileges. <literal>@</literal>, <literal>-</literal>, and <literal>+</literal> may be used together and they
|
||||
can appear in any order.</para>
|
||||
|
||||
<para>If more than one command is specified, the commands are
|
||||
|
Loading…
Reference in New Issue
Block a user