|
|
1.1 root 1: .\" Copyright (c) 1980 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)kill.1 6.2 (Berkeley) 4/20/86
6: .\"
7: .TH KILL 1 "April 20, 1986"
8: .UC 4
9: .SH NAME
10: kill \- terminate a process with extreme prejudice
11: .SH SYNOPSIS
12: .B kill
13: [
14: .BR \- sig
15: ]
16: processid ...
17: .br
18: .B kill
19: .B \-l
20: .SH DESCRIPTION
21: .I Kill
22: sends the TERM (terminate, 15) signal to the specified processes.
23: If a signal name or number preceded by `\-' is given
24: as first argument, that signal is sent instead of
25: terminate
26: (see
27: .IR sigvec (2)).
28: The signal names are listed by
29: `kill \-l', and are as given in
30: .I /usr/include/signal.h,
31: stripped of the common SIG prefix.
32: .PP
33: The terminate signal will kill processes that do not catch the signal;
34: `kill \-9 ...' is a sure kill, as the KILL (9) signal cannot be caught.
35: By convention, if process number 0 is specified, all members
36: in the process group (i.e. processes resulting from
37: the current login) are signaled (but beware: this works only
38: if you use
39: .IR sh (1);
40: not if you use
41: .IR csh (1).)
42: Negative process numbers also have special meanings; see
43: .IR kill (2)
44: for details.
45: .PP
46: The killed processes must belong
47: to the current user unless
48: he is the super-user.
49: .PP
50: The process number of an asynchronous process
51: started with `&' is reported by the shell.
52: Process numbers can also be found by using
53: .IR ps (1).
54: .I Kill
55: is a built-in to
56: .IR csh (1);
57: it allows job specifiers of the form ``%...'' as arguments
58: so process id's are not as often used as
59: .I kill
60: arguments.
61: See
62: .IR csh (1)
63: for details.
64: .SH "SEE ALSO"
65: csh(1), ps(1), kill(2), sigvec(2)
66: .SH BUGS
67: A replacement for ``kill 0''
68: for
69: .IR csh (1)
70: users should be provided.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.