Un outil pour savoir si une commande est posix - retour accueil
git clone git://bebou.netlib.re/isposix
Log | Files | Refs | README |
kill.html (20860B)
1 <!-- Copyright 2001-2024 IEEE and The Open Group, All Rights Reserved -->
2 <!DOCTYPE HTML>
3 <html lang="en">
4 <head>
5 <meta name="generator" content="HTML Tidy for HTML5 for Linux version 5.8.0">
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
7 <link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group rhtm tool v1.2.4 -->
8 <!-- Copyright (c) 2001-2024 The Open Group, All Rights Reserved -->
9 <title>kill</title>
10 </head>
11 <body bgcolor="white">
12 <div class="NAVHEADER">
13 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
14 <tr class="nav">
15 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/join.html" accesskey="P"><<<
16 Previous</a></td>
17 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
18 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/lex.html" accesskey="N">Next >>></a></td>
19 </tr>
20 </table>
21 <hr align="left" width="100%"></div>
22 <script language="JavaScript" src="../jscript/codes.js"></script><basefont size="3">
23 <center><font size="2">The Open Group Base Specifications Issue 8<br>
24 IEEE Std 1003.1-2024<br>
25 Copyright © 2001-2024 The IEEE and The Open Group</font></center>
26 <hr size="2" noshade>
27 <a name="top" id="top"></a> <a name="kill" id="kill"></a> <a name="tag_20_64" id="tag_20_64"></a><!-- kill -->
28 <h4 class="mansect"><a name="tag_20_64_01" id="tag_20_64_01"></a>NAME</h4>
29 <blockquote>kill — terminate or signal processes</blockquote>
30 <h4 class="mansect"><a name="tag_20_64_02" id="tag_20_64_02"></a>SYNOPSIS</h4>
31 <blockquote class="synopsis">
32 <p><code><tt>kill</tt> <b>[</b><tt>-s</tt> <i>signal_name</i><b>]</b> <i>pid</i><tt>...<br>
33 <br>
34 kill -l</tt> <b>[</b><i>exit_status</i><b>]</b> <tt><br>
35 <br></tt></code></p>
36 <div class="box"><code><tt><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt=
37 "[Option Start]" border="0"> kill</tt> <b>[</b><tt>-</tt><i>signal_name</i><b>]</b> <i>pid</i><tt>...<br>
38 <br>
39 kill</tt> <b>[</b><tt>-</tt><i>signal_number</i><b>]</b> <i>pid</i><tt>... <img src="../images/opt-end.gif" alt="[Option End]"
40 border="0"></tt></code></div>
41 <tt><br></tt></blockquote>
42 <h4 class="mansect"><a name="tag_20_64_03" id="tag_20_64_03"></a>DESCRIPTION</h4>
43 <blockquote>
44 <p>The <i>kill</i> utility shall send a signal to the process or processes specified by each <i>pid</i> operand.</p>
45 <p>For each <i>pid</i> operand, the <i>kill</i> utility shall perform actions equivalent to the <a href=
46 "../functions/kill.html"><i>kill</i>()</a> function defined in the System Interfaces volume of POSIX.1-2024 called with the
47 following arguments:</p>
48 <ul>
49 <li>
50 <p>The value of the <i>pid</i> operand shall be used as the <i>pid</i> argument.</p>
51 </li>
52 <li>
53 <p>The <i>sig</i> argument is the value specified by the <b>-s</b> option, <b>-</b><i>signal_number</i> option, or the
54 <b>-</b><i>signal_name</i> option, or by SIGTERM, if none of these options is specified.</p>
55 </li>
56 </ul>
57 </blockquote>
58 <h4 class="mansect"><a name="tag_20_64_04" id="tag_20_64_04"></a>OPTIONS</h4>
59 <blockquote>
60 <p>The <i>kill</i> utility shall conform to XBD <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax
61 Guidelines</i></a> , <sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt=
62 "[Option Start]" border="0"> except that in the last two SYNOPSIS forms, the <b>-</b><i>signal_number</i> and
63 <b>-</b><i>signal_name</i> options are usually more than a single character. <img src="../images/opt-end.gif" alt="[Option End]"
64 border="0"></p>
65 <p>The following options shall be supported:</p>
66 <dl compact>
67 <dd></dd>
68 <dt><b>-l</b></dt>
69 <dd>(The letter ell.) Write all values of <i>signal_name</i> supported by the implementation, if no operand is given. If an
70 <i>exit_status</i> operand is given and it is a value of the <tt>'?'</tt> shell special parameter (see <a href=
71 "../utilities/V3_chap02.html#tag_19_05_02"><i>2.5.2 Special Parameters</i></a> and <a href=
72 "../utilities/wait.html"><i>wait</i></a>) corresponding to a process that was terminated or stopped by a signal, the
73 <i>signal_name</i> corresponding to the signal that terminated or stopped the process shall be written. If an <i>exit_status</i>
74 operand is given and it is the unsigned decimal integer value of a signal number, the <i>signal_name</i> (the symbolic constant
75 name without the <b>SIG</b> prefix defined in the Base Definitions volume of POSIX.1-2024) corresponding to that signal shall be
76 written. Otherwise, the results are unspecified.</dd>
77 <dt><b>-s </b><i>signal_name</i></dt>
78 <dd><br>
79 Specify the signal to send, using one of the symbolic names defined in the <a href=
80 "../basedefs/signal.h.html"><i><signal.h></i></a> header. Values of <i>signal_name</i> shall be recognized in a
81 case-independent fashion, without the <b>SIG</b> prefix. In addition, the symbolic name 0 shall be recognized, representing the
82 signal value zero. The corresponding signal shall be sent instead of SIGTERM.</dd>
83 <dt><b>-</b><i>signal_name</i></dt>
84 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
85 "0"><br>
86 Equivalent to <b>-s</b> <i>signal_name</i>. <img src="../images/opt-end.gif" alt="[Option End]" border="0"></dd>
87 <dt><b>-</b><i>signal_number</i></dt>
88 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
89 "0"><br>
90 Specify a non-negative decimal integer, <i>signal_number</i>, representing the signal to be used instead of SIGTERM, as the
91 <i>sig</i> argument in the effective call to <a href="../functions/kill.html"><i>kill</i>()</a>. The correspondence between integer
92 values and the <i>sig</i> value used is shown in the following list.
93 <p>The effects of specifying any <i>signal_number</i> other than those listed below are undefined.</p>
94 <dl compact>
95 <dd></dd>
96 <dt>0</dt>
97 <dd>0</dd>
98 <dt>1</dt>
99 <dd>SIGHUP</dd>
100 <dt>2</dt>
101 <dd>SIGINT</dd>
102 <dt>3</dt>
103 <dd>SIGQUIT</dd>
104 <dt>6</dt>
105 <dd>SIGABRT</dd>
106 <dt>9</dt>
107 <dd>SIGKILL</dd>
108 <dt>14</dt>
109 <dd>SIGALRM</dd>
110 <dt>15</dt>
111 <dd>SIGTERM</dd>
112 </dl>
113 <p>If the first argument is a negative integer, it shall be interpreted as a <b>-</b><i>signal_number</i> option, not as a negative
114 <i>pid</i> operand specifying a process group. <img src="../images/opt-end.gif" alt="[Option End]" border="0"></p>
115 </dd>
116 </dl>
117 </blockquote>
118 <h4 class="mansect"><a name="tag_20_64_05" id="tag_20_64_05"></a>OPERANDS</h4>
119 <blockquote>
120 <p>The following operands shall be supported:</p>
121 <dl compact>
122 <dd></dd>
123 <dt><i>pid</i></dt>
124 <dd>One of the following:
125 <ol>
126 <li>
127 <p>A decimal integer specifying a process or process group to be signaled. The process or processes selected by positive, negative,
128 and zero values of the <i>pid</i> operand shall be as described for the <a href="../functions/kill.html"><i>kill</i>()</a>
129 function. If process number 0 is specified, all processes in the current process group shall be signaled. For the effects of
130 negative <i>pid</i> numbers, see the <a href="../functions/kill.html"><i>kill</i>()</a> function defined in the System Interfaces
131 volume of POSIX.1-2024. If the first <i>pid</i> operand is negative, it should be preceded by <tt>"--"</tt> to keep it from being
132 interpreted as an option.</p>
133 </li>
134 <li>
135 <p>A job ID (see XBD <a href="../basedefs/V1_chap03.html#tag_03_182"><i>3.182 Job ID</i></a> ) that identifies a process group in
136 the case of a job-control background job, or a process ID in the case of a non-job-control background job (if supported), to be
137 signaled. The job ID notation is applicable only for invocations of <i>kill</i> in the current shell execution environment; see
138 <a href="../utilities/V3_chap02.html#tag_19_13"><i>2.13 Shell Execution Environment</i></a> . <basefont size="2"></p>
139 <dl>
140 <dt><b>Note:</b></dt>
141 <dd>The job ID type of <i>pid</i> is only available on systems supporting the User Portability Utilities option or supporting
142 non-job-control background jobs.</dd>
143 </dl>
144 <basefont size="3"></li>
145 </ol>
146 </dd>
147 <dt><i>exit_status</i></dt>
148 <dd>A decimal integer specifying a signal number or the exit status of a process terminated by a signal.</dd>
149 </dl>
150 </blockquote>
151 <h4 class="mansect"><a name="tag_20_64_06" id="tag_20_64_06"></a>STDIN</h4>
152 <blockquote>
153 <p>Not used.</p>
154 </blockquote>
155 <h4 class="mansect"><a name="tag_20_64_07" id="tag_20_64_07"></a>INPUT FILES</h4>
156 <blockquote>
157 <p>None.</p>
158 </blockquote>
159 <h4 class="mansect"><a name="tag_20_64_08" id="tag_20_64_08"></a>ENVIRONMENT VARIABLES</h4>
160 <blockquote>
161 <p>The following environment variables shall affect the execution of <i>kill</i>:</p>
162 <dl compact>
163 <dd></dd>
164 <dt><i>LANG</i></dt>
165 <dd>Provide a default value for the internationalization variables that are unset or null. (See XBD <a href=
166 "../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization Variables</i></a> for the precedence of internationalization
167 variables used to determine the values of locale categories.)</dd>
168 <dt><i>LC_ALL</i></dt>
169 <dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
170 <dt><i>LC_CTYPE</i></dt>
171 <dd>Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as
172 opposed to multi-byte characters in arguments).</dd>
173 <dt><i>LC_MESSAGES</i></dt>
174 <dd><br>
175 Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.</dd>
176 <dt><i>NLSPATH</i></dt>
177 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0">
178 Determine the location of messages objects and message catalogs. <img src="../images/opt-end.gif" alt="[Option End]" border=
179 "0"></dd>
180 </dl>
181 </blockquote>
182 <h4 class="mansect"><a name="tag_20_64_09" id="tag_20_64_09"></a>ASYNCHRONOUS EVENTS</h4>
183 <blockquote>
184 <p>Default.</p>
185 </blockquote>
186 <h4 class="mansect"><a name="tag_20_64_10" id="tag_20_64_10"></a>STDOUT</h4>
187 <blockquote>
188 <p>When the <b>-l</b> option is not specified, the standard output shall not be used.</p>
189 <p>When the <b>-l</b> option is specified, the symbolic name of each signal shall be written in the following format:</p>
190 <pre>
191 <tt>"%s%c", <</tt><i>signal_name</i><tt>>, <</tt><i>separator</i><tt>>
192 </tt></pre>
193 <p>where the <<i>signal_name</i>> is in uppercase, without the <b>SIG</b> prefix, and the <<i>separator</i>> shall be
194 either a <newline> or a <space>. For the last signal written, <<i>separator</i>> shall be a <newline>.</p>
195 <p>When both the <b>-l</b> option and <i>exit_status</i> operand are specified, the symbolic name of the corresponding signal shall
196 be written in the following format:</p>
197 <pre>
198 <tt>"%s\n", <</tt><i>signal_name</i><tt>>
199 </tt></pre></blockquote>
200 <h4 class="mansect"><a name="tag_20_64_11" id="tag_20_64_11"></a>STDERR</h4>
201 <blockquote>
202 <p>The standard error shall be used only for diagnostic messages.</p>
203 </blockquote>
204 <h4 class="mansect"><a name="tag_20_64_12" id="tag_20_64_12"></a>OUTPUT FILES</h4>
205 <blockquote>
206 <p>None.</p>
207 </blockquote>
208 <h4 class="mansect"><a name="tag_20_64_13" id="tag_20_64_13"></a>EXTENDED DESCRIPTION</h4>
209 <blockquote>
210 <p>None.</p>
211 </blockquote>
212 <h4 class="mansect"><a name="tag_20_64_14" id="tag_20_64_14"></a>EXIT STATUS</h4>
213 <blockquote>
214 <p>The following exit values shall be returned:</p>
215 <dl compact>
216 <dd></dd>
217 <dt> 0</dt>
218 <dd>The <b>-l</b> option was specified and the output specified in STDOUT was successfully written to standard output; or, the
219 <b>-l</b> option was not specified, at least one matching process was found for each <i>pid</i> operand, and the specified signal
220 was successfully processed for at least one matching process.</dd>
221 <dt>>0</dt>
222 <dd>An error occurred.</dd>
223 </dl>
224 </blockquote>
225 <h4 class="mansect"><a name="tag_20_64_15" id="tag_20_64_15"></a>CONSEQUENCES OF ERRORS</h4>
226 <blockquote>
227 <p>Default.</p>
228 </blockquote>
229 <hr>
230 <div class="box"><em>The following sections are informative.</em></div>
231 <h4 class="mansect"><a name="tag_20_64_16" id="tag_20_64_16"></a>APPLICATION USAGE</h4>
232 <blockquote>
233 <p>This utility is required to be intrinsic. See <a href="../utilities/V3_chap01.html#tag_18_07"><i>1.7 Intrinsic Utilities</i></a>
234 for details.</p>
235 <p>Process numbers can be found by using <a href="../utilities/ps.html"><i>ps</i></a>.</p>
236 <p>The use of job ID notation is not dependent on job control being enabled. When job control has been disabled using <a href=
237 "../utilities/set.html"><i>set</i></a> <b>+m</b>, <i>kill</i> can still be used to signal the process group associated with a
238 job-control background job, or the process ID associated with a non-control background job (if supported), using</p>
239 <pre>
240 <tt>kill %<</tt><i>background job number</i><tt>>
241 </tt></pre>
242 <p>See also the RATIONALE for <a href="../utilities/jobs.html"><i>jobs</i></a> and <a href=
243 "../utilities/wait.html"><i>wait</i></a>.</p>
244 <p>The job ID notation is not required to work as expected when <i>kill</i> is operating in its own utility execution environment.
245 In either of the following examples:</p>
246 <pre>
247 <tt>nohup kill %1 &
248 system("kill %1");
249 </tt></pre>
250 <p>the <i>kill</i> operates in a different environment and does not share the shell's understanding of job numbers.</p>
251 </blockquote>
252 <h4 class="mansect"><a name="tag_20_64_17" id="tag_20_64_17"></a>EXAMPLES</h4>
253 <blockquote>
254 <p>Any of the commands:</p>
255 <pre>
256 <tt>kill -9 100 -165
257 kill -s kill 100 -165
258 kill -s KILL 100 -165
259 </tt></pre>
260 <p>sends the SIGKILL signal to the process whose process ID is 100 and to all processes whose process group ID is 165, assuming the
261 sending process has permission to send that signal to the specified processes, and that they exist.</p>
262 <p>The System Interfaces volume of POSIX.1-2024 and this volume of POSIX.1-2024 do not require specific signal numbers for any
263 <i>signal_names</i>. Even the <b>-</b><i>signal_number</i> option provides symbolic (although numeric) names for signals. If a
264 process is terminated by a signal, its exit status indicates the signal that killed it, but the exact values are not specified. The
265 <i>kill</i> <b>-l</b> option, however, can be used to map decimal signal numbers and exit status values into the name of a signal.
266 The following example reports the status of a terminated job:</p>
267 <pre>
268 <tt>job
269 stat=$?
270 if [ $stat -eq 0 ]
271 then
272 echo job completed successfully.
273 elif [ $stat -gt 128 ]
274 then
275 echo job terminated by signal SIG$(kill -l $stat).
276 else
277 echo job terminated with error code $stat.
278 fi
279 </tt></pre>
280 <p>To send the default signal to a process group (say 123), an application should use a command similar to one of the
281 following:</p>
282 <pre>
283 <tt>kill -s TERM -- -123
284 kill -- -123
285 </tt></pre></blockquote>
286 <h4 class="mansect"><a name="tag_20_64_18" id="tag_20_64_18"></a>RATIONALE</h4>
287 <blockquote>
288 <p>The <b>-l</b> option originated from the C shell, and is also implemented in the KornShell. The C shell output can consist of
289 multiple output lines because the signal names do not always fit on a single line on some terminal screens. The KornShell output
290 also included the implementation-defined signal numbers and was considered by the standard developers to be too difficult for
291 scripts to parse conveniently. The specified output format is intended not only to accommodate the historical C shell output, but
292 also to permit an entirely vertical or entirely horizontal listing on systems for which this is appropriate.</p>
293 <p>An early proposal invented the name SIGNULL as a <i>signal_name</i> for signal 0 (used by the System Interfaces volume of
294 POSIX.1-2024 to test for the existence of a process without sending it a signal). Since the <i>signal_name</i> 0 can be used in
295 this case unambiguously, SIGNULL has been removed.</p>
296 <p>An early proposal also required symbolic <i>signal_name</i>s to be recognized with or without the <b>SIG</b> prefix. Historical
297 versions of <i>kill</i> have not written the <b>SIG</b> prefix for the <b>-l</b> option and have not recognized the <b>SIG</b>
298 prefix on <i>signal_name</i>s. Since neither applications portability nor ease-of-use would be improved by requiring this
299 extension, it is no longer required.</p>
300 <p>To avoid an ambiguity of an initial negative number argument specifying either a signal number or a process group, POSIX.1-2024
301 mandates that it is always considered the former by implementations that support the XSI option. It also requires that conforming
302 applications always use the <tt>"--"</tt> options terminator argument when specifying a process group.</p>
303 <p>The <b>-s</b> option was added in response to international interest in providing some form of <i>kill</i> that meets the
304 Utility Syntax Guidelines.</p>
305 <p>The job ID notation is not required to work as expected when <i>kill</i> is operating in its own utility execution environment.
306 In either of the following examples:</p>
307 <pre>
308 <tt>nohup kill %1 &
309 system("kill %1");
310 </tt></pre>
311 <p>the <i>kill</i> operates in a different environment and does not understand how the shell has managed its job numbers.</p>
312 </blockquote>
313 <h4 class="mansect"><a name="tag_20_64_19" id="tag_20_64_19"></a>FUTURE DIRECTIONS</h4>
314 <blockquote>
315 <p>None.</p>
316 </blockquote>
317 <h4 class="mansect"><a name="tag_20_64_20" id="tag_20_64_20"></a>SEE ALSO</h4>
318 <blockquote>
319 <p><a href="../utilities/V3_chap02.html#tag_19"><i>2. Shell Command Language</i></a> , <a href=
320 "../utilities/ps.html#"><i>ps</i></a> , <a href="../utilities/wait.html#tag_20_147"><i>wait</i></a></p>
321 <p>XBD <a href="../basedefs/V1_chap03.html#tag_03_182"><i>3.182 Job ID</i></a> , <a href="../basedefs/V1_chap08.html#tag_08"><i>8.
322 Environment Variables</i></a> , <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax Guidelines</i></a> , <a href=
323 "../basedefs/signal.h.html"><i><signal.h></i></a></p>
324 <p>XSH <a href="../functions/kill.html#tag_17_296"><i>kill</i></a></p>
325 </blockquote>
326 <h4 class="mansect"><a name="tag_20_64_21" id="tag_20_64_21"></a>CHANGE HISTORY</h4>
327 <blockquote>
328 <p>First released in Issue 2.</p>
329 </blockquote>
330 <h4 class="mansect"><a name="tag_20_64_22" id="tag_20_64_22"></a>Issue 6</h4>
331 <blockquote>
332 <p>The obsolescent versions of the SYNOPSIS are turned into non-obsolescent features of the XSI option, corresponding to a similar
333 change in the <a href="../utilities/V3_chap02.html#trap"><i>trap</i></a> special built-in.</p>
334 </blockquote>
335 <h4 class="mansect"><a name="tag_20_64_23" id="tag_20_64_23"></a>Issue 7</h4>
336 <blockquote>
337 <p>SD5-XCU-ERN-97 is applied, updating the SYNOPSIS.</p>
338 </blockquote>
339 <h4 class="mansect"><a name="tag_20_64_24" id="tag_20_64_24"></a>Issue 8</h4>
340 <blockquote>
341 <p>Austin Group Defect 854 is applied, adding a note to the APPLICATION USAGE section that this utility is required to be
342 intrinsic.</p>
343 <p>Austin Group Defect 1122 is applied, changing the description of <i>NLSPATH .</i></p>
344 <p>Austin Group Defect 1254 is applied, clarifying the <b>-l</b> option with regard to an <i>exit_status</i> operand corresponding
345 to a stopped process, changing "job control job ID" to "job ID", and adding a paragraph to the RATIONALE section.</p>
346 <p>Austin Group Defect 1260 is applied, changing the SYNOPSIS and EXAMPLES sections in relation to the <b>-s</b> option, and the
347 RATIONALE section in relation to the use of <tt>"--"</tt> when specifying a process group.</p>
348 <p>Austin Group Defect 1504 is applied, changing the EXIT STATUS section.</p>
349 </blockquote>
350 <div class="box"><em>End of informative text.</em></div>
351 <hr>
352 <p> </p>
353 <a href="#top"><span class="topOfPage">return to top of page</span></a><br>
354 <hr size="2" noshade>
355 <center><font size="2">UNIX® is a registered Trademark of The Open Group.<br>
356 POSIX™ is a Trademark of The IEEE.<br>
357 Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved<br>
358 [ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
359 "../functions/contents.html">XSH</a> | <a href="../utilities/contents.html">XCU</a> | <a href="../xrat/contents.html">XRAT</a>
360 ]</font></center>
361 <hr size="2" noshade>
362 <div class="NAVHEADER">
363 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
364 <tr class="nav">
365 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/join.html" accesskey="P"><<<
366 Previous</a></td>
367 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
368 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/lex.html" accesskey="N">Next >>></a></td>
369 </tr>
370 </table>
371 <hr align="left" width="100%"></div>
372 </body>
373 </html>