Searched full:killsnoop (Results 1 – 7 of 7) sorted by relevance
1 Demonstrations of killsnoop, the Linux eBPF/bcc version.6 # ./killsnoop21 # ./killsnoop -h22 usage: killsnoop [-h] [-x] [-p PID]32 ./killsnoop # trace all kill() signals33 ./killsnoop -x # only show failed kills34 ./killsnoop -p 181 # only trace PID 18135 ./killsnoop -s 9 # only trace signal 9
4 # killsnoop Trace signals issued by the kill() syscall.7 # USAGE: killsnoop [-h] [-x] [-p PID]23 ./killsnoop # trace all kill() signals24 ./killsnoop -x # only show failed kills25 ./killsnoop -p 181 # only trace PID 18126 ./killsnoop -s 9 # only trace signal 9
1 .TH killsnoop 8 "2015-08-20" "USER COMMANDS"3 killsnoop \- Trace signals issued by the kill() syscall. Uses Linux eBPF/bcc.5 .B killsnoop [\-h] [\-x] [-p PID]7 killsnoop traces the kill() syscall, to show signals sent via this method. This38 .B killsnoop42 .B killsnoop \-x46 .B killsnoop \-p 18150 .B killsnoop \-s 9
4 # killsnoop Trace signals issued by the kill() syscall.7 # USAGE: killsnoop [-h] [-t] [-x] [-p PID]20 ./killsnoop # trace all kill() signals21 ./killsnoop -t # include timestamps22 ./killsnoop -x # only show failed kills23 ./killsnoop -p 181 # only trace PID 181
212 # Because killsnoop intercepts signals, if we send it a SIGINT we we216 # To reproduce the above issue, run killsnoop and in another shell run217 # `kill -s SIGINT $(pidof python)`. As a result, killsnoop will print219 self.run_with_int("killsnoop.py", kill=True)
194 killsnoop:195 command: bcc-wrapper killsnoop
126 - tools/[killsnoop](tools/killsnoop.py): Trace signals issued by the kill() syscall. [Examples](too…