Main index | Section 1 | 日本語 | Options |
The options are as follows:
| |
Trace descendants of the original traced process created by fork(2), vfork(2), etc. To distinguish events between processes, the process ID (PID) of the process is included in the output of each event. | |
| |
Show the argument strings that are passed in each execve(2) system call. | |
| |
Do not display individual system calls or signals. Instead, before exiting, print a summary containing for each system call: the total system time used, the number of times the call was invoked, and the number of times the call returned with an error. | |
| |
Show the environment strings that are passed in each execve(2) system call. | |
| |
Include timestamps in the output showing the time elapsed since the trace was started. | |
| |
Include timestamps in the output showing the time elapsed since the last recorded event. | |
| |
Include the thread ID of in the output of each event. | |
| |
Do not display information about signals received by the process. (Normally, truss displays signal as well as system call events.) | |
| |
Print the output to the specified file instead of standard error. | |
| |
Display strings using at most strsize characters. If the buffer is larger, "..." will be displayed at the end of the string. The default strsize is 32. | |
| |
Follow the process specified by pid instead of a new command. | |
command [args] | |
Execute
command
and trace the system calls of it.
(The
| |
$ truss /bin/echo hello
Do the same, but put the output into a file:
$ truss -o /tmp/truss.out /bin/echo hello
Follow an already-running process:
$ truss -p 34
TRUSS (1) | July 24, 2017 |
Main index | Section 1 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | The “N” in NFS stands for Not, or Need, or perhaps Nightmare | ” |
— Harry Spencer |