1 .TH dtruss 1m "$Date:: 2007-08-05 #$" "USER COMMANDS"
3 dtruss \- process syscall details. Uses DTrace.
6 [\-acdeflhoLs] [\-t syscall] { \-p PID | \-n name | command }
8 dtruss prints details on process system calls. It is like a DTrace
9 version of truss, and has been designed to be less intrusive than
12 Of particular interest is the elapsed times and on cpu times, which
13 can identify both system calls that are slow to complete, and those
14 which are consuming CPU cycles.
16 Since this uses DTrace, only the root user or users with the
17 dtrace_kernel privilege can run this command.
21 stable - needs the syscall provider.
28 dynamic variable buffer size. Increase this if you notice dynamic
29 variable drop errors. The default is "4m" for 4 megabytes per CPU.
32 print system call counts
35 print relative timestamps, us
38 print elapsed times, us
41 follow children as they are forked
44 force printing of pid/lwpid per line
47 don't print pid/lwpid per line
50 examine processes with this name
53 print on-cpu times, us
56 print stack backtraces
62 examine this syscall only
66 run and examine the "df -h" command
78 examine all processes called "tar"
84 run test.sh and follow children
89 run the "date" command and print elapsed and on cpu times,
97 Process ID / Lightweight Process ID
100 relative timestamps to the start of the thread, us (microseconds)
103 elapsed time for this system call, us
106 on-cpu time for this system call, us
109 system call name, with arguments (some may be evaluated)
112 See the DTraceToolkit for further documentation under the
113 Docs directory. The DTraceToolkit docs may include full worked
114 examples with verbose descriptions explaining the output.
116 dtruss will run forever until Ctrl\-C is hit, or if a command was
117 executed dtruss will finish when the command ends.
122 procsystime(1M), dtrace(1M), truss(1)