Searched full:opensnoop (Results 1 – 18 of 18) sorted by relevance
| /external/bcc/tools/ |
| D | opensnoop_example.txt | 1 Demonstrations of opensnoop, the Linux eBPF/bcc version.
4 opensnoop traces the open() syscall system-wide, and prints various details.
7 # ./opensnoop
46 opensnoop can be useful for discovering configuration and log files, if used
53 ./opensnoop -Tp 1956
70 # ./opensnoop -x
95 # ./opensnoop -d 2
106 # ./opensnoop -n ed
137 # ./opensnoop -h
138 usage: opensnoop [-h] [-T] [-x] [-p PID] [-t TID] [-d DURATION] [-n NAME]
[all …]
|
| D | opensnoop.py | 4 # opensnoop Trace open() syscalls.
7 # USAGE: opensnoop [-h] [-T] [-x] [-p PID] [-d DURATION] [-t TID] [-n NAME]
24 ./opensnoop # trace all open() syscalls
25 ./opensnoop -T # include timestamps
26 ./opensnoop -x # only show failed opens
27 ./opensnoop -p 181 # only trace PID 181
28 ./opensnoop -t 123 # only trace TID 123
29 ./opensnoop -d 10 # trace for 10 seconds only
30 ./opensnoop -n main # only print process names containing "main"
|
| D | syscount_example.txt | 83 might be worth investigating with follow-up tools like opensnoop, execsnoop,
111 investigating with follow-up tools like opensnoop, execsnoop, or
|
| D | statsnoop_example.txt | 53 to opensnoop, which shows what files were actually opened.
|
| /external/bcc/man/man8/ |
| D | opensnoop.8 | 1 .TH opensnoop 8 "2015-08-18" "USER COMMANDS"
3 opensnoop \- Trace open() syscalls. Uses Linux eBPF/bcc.
5 .B opensnoop [\-h] [\-T] [\-x] [\-p PID] [\-t TID] [\-d DURATION] [\-n name]
7 opensnoop traces the open() syscall, showing which processes are attempting
48 .B opensnoop
52 .B opensnoop -d 10
56 .B opensnoop \-T
60 .B opensnoop \-x
64 .B opensnoop \-p 181
68 .B opensnoop \-n ed
|
| D | bashreadline.8 | 52 opensnoop(8)
|
| D | ttysnoop.8 | 60 opensnoop(1)
|
| D | killsnoop.8 | 83 opensnoop(8), funccount(8)
|
| D | filelife.8 | 72 opensnoop(1)
|
| D | statsnoop.8 | 91 opensnoop(1)
|
| D | execsnoop.8 | 107 opensnoop(1)
|
| /external/bcc/tools/old/ |
| D | opensnoop.py | 4 # opensnoop Trace open() syscalls.
7 # USAGE: opensnoop [-h] [-t] [-x] [-p PID]
20 ./opensnoop # trace all open() syscalls
21 ./opensnoop -t # include timestamps
22 ./opensnoop -x # only show failed opens
23 ./opensnoop -p 181 # only trace PID 181
|
| /external/bcc/snapcraft/ |
| D | README.md | 30 Now run a bcc tool, for example, to run opensnoop use:
32 sudo bcc.opensnoop
|
| D | snapcraft.yaml | 180 opensnoop:
181 command: wrapper opensnoop
182 aliases: [opensnoop]
|
| /external/bcc/docs/ |
| D | tutorial.md | 31 1. opensnoop
62 #### 1.2. opensnoop
65 # ./opensnoop
79 opensnoop prints one line of output for each open() syscall, including details.
81 …y, when they are constantly attempting to read files that do not exist. opensnoop gives you a quic…
|
| /external/adeb/ |
| D | BCC.md | 44 `opensnoop` or any of the other BCC tracers to confirm that the setup worked
|
| /external/bcc/ |
| D | README.md | 128 - tools/[opensnoop](tools/opensnoop.py): Trace open() syscalls. [Examples](tools/opensnoop_example.…
|
| /external/bcc/tests/python/ |
| D | test_tools_smoke.py | 249 self.run_with_int("opensnoop.py")
|