Re: Truncated truss output
From: Tony Walton (tony.walton_at_s_u_n.com)
Date: 06/04/04
- Next message: Chris Morgan: "Re: Sun, Fujitsu to merge server lines by 2006"
- Previous message: Casper H.S. ***: "Re: Compat mode for passwd and ldap"
- In reply to: John Schmidt: "Truncated truss output"
- Next in thread: John Schmidt: "Re: Truncated truss output"
- Reply: John Schmidt: "Re: Truncated truss output"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 04 Jun 2004 14:45:23 +0100
John Schmidt wrote:
>
> Is there something basic I'm missing? None of the command line args
> in the man page have the desired effect (printing *everything* being
> written) as far as I can figure out.
From the truss(1) manual page:
-r [!]fd,...
Shows the full contents of the I/O buffer for each
read() on any of the specified file descriptors. The
output is formatted 32 bytes per line and shows each
byte as an ASCII character (preceded by one blank) or
as a 2-character C language escape sequence for con-
trol characters such as horizontal tab (\t) and new-
line (\n). If ASCII interpretation is not possible,
the byte is shown in 2-character hexadecimal represen-
tation. (The first 12 bytes of the I/O buffer for each
traced read() are shown even in the absence of -r.)
Default is -r!all.
-w [!]fd,...
Shows the contents of the I/O buffer for each write()
on any of the specified file descriptors (see the -r
option). Default is -w!all.
Regards
-- Tony
- Next message: Chris Morgan: "Re: Sun, Fujitsu to merge server lines by 2006"
- Previous message: Casper H.S. ***: "Re: Compat mode for passwd and ldap"
- In reply to: John Schmidt: "Truncated truss output"
- Next in thread: John Schmidt: "Re: Truncated truss output"
- Reply: John Schmidt: "Re: Truncated truss output"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]