200 \fB\fB-o\fR \fIoutfile\fR\fR
 201 .ad
 202 .sp .6
 203 .RS 4n
 204 File to be used for the trace output. By default, the output goes to standard
 205 error.
 206 .RE
 207 
 208 .sp
 209 .ne 2
 210 .na
 211 \fB\fB-p\fR\fR
 212 .ad
 213 .sp .6
 214 .RS 4n
 215 Interprets the \fIcommand\fR arguments to \fBtruss\fR as a list of process-ids
 216 for existing processes (see \fBps\fR(1)) rather than as a command to be
 217 executed. \fBtruss\fR takes control of each process and begins tracing it
 218 provided that the userid and groupid of the process match those of the user or
 219 that the user is a privileged user. Users can trace only selected threads by
 220 appending \fB/\fR\fIthread-id\fR to the process-id. Mutiple threads can be
 221 selected using the \fB-\fR and \fB,\fR delimiters. For example \fB/1,2,7-9\fR
 222 traces threads \fB1\fR, \fB2\fR, \fB7\fR, \fB8\fR, and \fB9\fR. Processes can
 223 also be specified by their names in the \fB/proc\fR directory, for example,
 224 \fB/proc/12345\fR.
 225 .RE
 226 
 227 .sp
 228 .ne 2
 229 .na
 230 \fB\fB-r\fR [\fB!\fR]\fIfd\fR,...\fR
 231 .ad
 232 .sp .6
 233 .RS 4n
 234 Shows the full contents of the \fBI/O\fR buffer for each \fBread()\fR on any of
 235 the specified file descriptors. The output is formatted 32 bytes per line and
 236 shows each byte as an \fBASCII\fR character (preceded by one blank) or as a
 237 2-character C language escape sequence for control characters such as
 238 horizontal tab (\|\e\|t) and newline (\|\e\|n). If \fBASCII\fR interpretation
 239 is not possible, the byte is shown in 2-character hexadecimal representation.
 240 (The first 12 bytes of the \fBI/O\fR buffer for each traced \fBprint >read()\fR

 200 \fB\fB-o\fR \fIoutfile\fR\fR
 201 .ad
 202 .sp .6
 203 .RS 4n
 204 File to be used for the trace output. By default, the output goes to standard
 205 error.
 206 .RE
 207 
 208 .sp
 209 .ne 2
 210 .na
 211 \fB\fB-p\fR\fR
 212 .ad
 213 .sp .6
 214 .RS 4n
 215 Interprets the \fIcommand\fR arguments to \fBtruss\fR as a list of process-ids
 216 for existing processes (see \fBps\fR(1)) rather than as a command to be
 217 executed. \fBtruss\fR takes control of each process and begins tracing it
 218 provided that the userid and groupid of the process match those of the user or
 219 that the user is a privileged user. Users can trace only selected threads by
 220 appending \fB/\fR\fIthread-id\fR to the process-id. Multiple threads can be
 221 selected using the \fB-\fR and \fB,\fR delimiters. For example \fB/1,2,7-9\fR
 222 traces threads \fB1\fR, \fB2\fR, \fB7\fR, \fB8\fR, and \fB9\fR. Processes can
 223 also be specified by their names in the \fB/proc\fR directory, for example,
 224 \fB/proc/12345\fR.
 225 .RE
 226 
 227 .sp
 228 .ne 2
 229 .na
 230 \fB\fB-r\fR [\fB!\fR]\fIfd\fR,...\fR
 231 .ad
 232 .sp .6
 233 .RS 4n
 234 Shows the full contents of the \fBI/O\fR buffer for each \fBread()\fR on any of
 235 the specified file descriptors. The output is formatted 32 bytes per line and
 236 shows each byte as an \fBASCII\fR character (preceded by one blank) or as a
 237 2-character C language escape sequence for control characters such as
 238 horizontal tab (\|\e\|t) and newline (\|\e\|n). If \fBASCII\fR interpretation
 239 is not possible, the byte is shown in 2-character hexadecimal representation.
 240 (The first 12 bytes of the \fBI/O\fR buffer for each traced \fBprint >read()\fR