|
138
|
1 <refentry id="kill">
|
|
|
2 <refnamediv>
|
|
|
3 <refname>KILL</refname>
|
|
|
4 <refpurpose>Abort a process</refpurpose>
|
|
|
5 </refnamediv>
|
|
|
6
|
|
|
7 <refsynopsisdiv>
|
|
|
8 <cmdsynopsis>
|
|
|
9 <command>KILL</command>
|
|
|
10 <arg choice="plain">
|
|
|
11 &replstart;procID&replend;
|
|
|
12 </arg>
|
|
|
13 </cmdsynopsis>
|
|
|
14 </refsynopsisdiv>
|
|
|
15
|
|
|
16 <refsect1><title>Description</title>
|
|
|
17 <para>
|
|
|
18 This shell "built in" command sends an "abort" signal to the
|
|
|
19 process having the process ID number specified. The process to be
|
|
|
20 aborted must have the same user ID as the user that executed the
|
|
|
21 command. The "procs" command can be used to obtain the process ID
|
|
|
22 numbers.
|
|
|
23 </para>
|
|
|
24 <para>
|
|
|
25 NOTE: If a process is waiting for I/O, it may not die until it
|
|
|
26 completes the current I/O operation, therefore, if you KILL a
|
|
|
27 process and the PROCS command shows it still exists, it is probably
|
|
|
28 waiting for receive a line of data from a terminal before it can
|
|
|
29 die.
|
|
|
30
|
|
|
31 Since this is a built-in SHELL command, it does not appear in the
|
|
|
32 CMDS directory.
|
|
|
33
|
|
|
34 For more information see: 4.5, 5.2, PROCS
|
|
|
35
|
|
|
36 </para>
|
|
|
37 </refsect1>
|
|
|
38 <refsect1><title>Examples</title>
|
|
|
39 <screen>
|
|
|
40
|
|
|
41 kill 5
|
|
|
42
|
|
|
43 kill 22
|
|
|
44
|
|
|
45 OS9: procs
|
|
|
46
|
|
|
47 User # Id pty state Mem Primary module
|
|
|
48 ----- --- --- -------- --- --------------
|
|
|
49 20 2 0 active 2 Shell <TERM
|
|
|
50 20 1 0 waiting 1 Sysgo <TERM
|
|
|
51 20 3 0 sleeping 20 Copy <TERM
|
|
|
52
|
|
|
53 OS9: kill 3
|
|
|
54 OS9: procs
|
|
|
55
|
|
|
56 User # Id pty state Mem Primary module
|
|
|
57 ----- --- --- -------- --- --------------
|
|
|
58 20 2 0 active 2 Shell <TERM
|
|
|
59 20 1 0 waiting 1 Sysgo <TERM
|
|
|
60
|
|
|
61 OS9:
|
|
|
62 </screen>
|
|
|
63 </refsect1>
|
|
|
64 </refentry>
|
|
|
65
|
