1killsnoop(8) System Manager's Manual killsnoop(8)
2
3
4
6 killsnoop - Trace signals issued by the kill() syscall. Uses Linux
7 eBPF/bcc.
8
10 killsnoop [-h] [-x] [-p PID]
11
13 killsnoop traces the kill() syscall, to show signals sent via this
14 method. This may be useful to troubleshoot failing applications, where
15 an unknown mechanism is sending signals.
16
17 This works by tracing the kernel sys_kill() function using dynamic
18 tracing, and will need updating to match any changes to this function.
19
20 This makes use of a Linux 4.5 feature (bpf_perf_event_output()); for
21 kernels older than 4.5, see the version under tools/old, which uses an
22 older mechanism.
23
24 Since this uses BPF, only the root user can use this tool.
25
27 CONFIG_BPF and bcc.
28
30 -h Print usage message.
31
32 -x Only print failed kill() syscalls.
33
34 -p PID Trace this process ID only (filtered in-kernel).
35
37 Trace all kill() syscalls:
38 # killsnoop
39
40 Trace only kill() syscalls that failed:
41 # killsnoop -x
42
43 Trace PID 181 only:
44 # killsnoop -p 181
45
47 TIME Time of the kill call.
48
49 PID Source process ID
50
51 COMM Source process name
52
53 SIG Signal number. See signal(7).
54
55 TPID Target process ID
56
57 RES Result. 0 == success, a negative value (of the error code) for
58 failure.
59
61 This traces the kernel kill function and prints output for each event.
62 As the rate of this is generally expected to be low (< 100/s), the
63 overhead is also expected to be negligible. If you have an application
64 that is calling a very high rate of kill()s for some reason, then test
65 and understand overhead before use.
66
68 This is from bcc.
69
70 https://github.com/iovisor/bcc
71
72 Also look in the bcc distribution for a companion _examples.txt file
73 containing example usage, output, and commentary for this tool.
74
76 Linux
77
79 Unstable - in development.
80
82 Brendan Gregg
83
85 opensnoop(8), funccount(8)
86
87
88
89USER COMMANDS 2015-08-20 killsnoop(8)