1strace(1M) System Administration Commands strace(1M)
2
3
4
6 strace - print STREAMS trace messages
7
9 strace [mid sid level]...
10
11
13 strace without arguments writes all STREAMS event trace messages from
14 all drivers and modules to its standard output. These messages are
15 obtained from the STREAMS log driver (see log(7D)). If arguments are
16 provided, they must be in triplets of the form mid, sid, level, where
17 mid is a STREAMS module ID number, sid is a sub-ID number, and level
18 is a tracing priority level. Each triplet indicates that tracing mes‐
19 sages are to be received from the given module/driver, sub-ID (usually
20 indicating minor device), and priority level equal to, or less than the
21 given level. The token all may be used for any member to indicate no
22 restriction for that attribute.
23
24
25 The format of each trace message output is:
26
27
28 <seq> <time> <ticks> <level> <flags> <mid> <sid> <text>
29
30 <seq> trace sequence number
31
32
33 <time> time of message in hh:mm:ss
34
35
36 <ticks> time of message in machine ticks since boot
37
38
39 <level> tracing priority level
40
41
42 <flags> E : message is also in the error log F : indicates a fatal
43 error N : mail was sent to the system administrator (hard‐
44 coded as root)
45
46
47 <mid> module ID number of source
48
49
50 <sid> sub-ID number of source
51
52
53 <text> formatted text of the trace message
54
55
56
57 Once initiated, strace will continue to execute until terminated by the
58 user.
59
61 Example 1 A sample output of the strace command:
62
63
64 The following example outputs all trace messages from the module or
65 driver whose module ID is 41:
66
67
68 strace 41 all all
69
70
71
72
73 The following example outputs those trace messages from driver or mod‐
74 ule ID 41 with sub-IDs 0, 1, or 2:
75
76
77 strace 41 0 1 41 1 1 41 2 0
78
79
80
81
82 Messages from sub-IDs 0 and 1 must have a tracing level less than or
83 equal to 1. Those from sub-ID 2 must have a tracing level of 0.
84
85
87 See attributes(5) for descriptions of the following attributes:
88
89
90
91
92 ┌─────────────────────────────┬─────────────────────────────┐
93 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
94 ├─────────────────────────────┼─────────────────────────────┤
95 │Availability │SUNWcsu │
96 └─────────────────────────────┴─────────────────────────────┘
97
99 attributes(5), log(7D)
100
101
102
103
105 o There is no restriction to the number of strace processes
106 opening the STREAMS log driver at a time.
107
108 o The log-driver records the list of the triplets specified in
109 the command invocation, and compares each potential trace
110 message against this list to decide if it should be format‐
111 ted and sent up to the strace process. Hence, long lists of
112 triplets will have a greater impact on overall STREAMS per‐
113 formance. Running strace will have the most impact on the
114 timing of the modules and drivers generating the trace mes‐
115 sages that are sent to the strace process. If trace messages
116 are generated faster than the strace process can handle
117 them, some of the messages will be lost. This last case can
118 be determined by examining the sequence numbers on the trace
119 messages output.
120
121
122
123SunOS 5.11 4 Oct 1994 strace(1M)