1 QA output created by 602
3 Usage: pmdatrace [options]
6 -d domain use domain (numeric) for metrics domain of PMDA
7 -l logfile write log into logfile rather than using default file
8 -A access host based access control
9 -I port expect programs to connect on given inet port (number/name)
10 -N buckets number of historical data buffers maintained
11 -T period time over which samples are considered (default 60 seconds)
12 -U units export observation values using the given units
13 -V units export counter values using the given units
15 --- Bad units specification #1 ---
16 pmdatrace: token parse error in string "1,1,1"
17 Usage: pmdatrace [options]
20 -d domain use domain (numeric) for metrics domain of PMDA
21 -l logfile write log into logfile rather than using default file
22 -A access host based access control
23 -I port expect programs to connect on given inet port (number/name)
24 -N buckets number of historical data buffers maintained
25 -T period time over which samples are considered (default 60 seconds)
26 -U units export observation values using the given units
27 -V units export counter values using the given units
29 --- Bad units specification #2 ---
30 pmdatrace: token parse error in string "1,,1,1,1,1"
31 Usage: pmdatrace [options]
34 -d domain use domain (numeric) for metrics domain of PMDA
35 -l logfile write log into logfile rather than using default file
36 -A access host based access control
37 -I port expect programs to connect on given inet port (number/name)
38 -N buckets number of historical data buffers maintained
39 -T period time over which samples are considered (default 60 seconds)
40 -U units export observation values using the given units
41 -V units export counter values using the given units
43 --- Bad units specification #3 ---
44 pmdatrace: integer parse error for substring "foo"
45 Usage: pmdatrace [options]
48 -d domain use domain (numeric) for metrics domain of PMDA
49 -l logfile write log into logfile rather than using default file
50 -A access host based access control
51 -I port expect programs to connect on given inet port (number/name)
52 -N buckets number of historical data buffers maintained
53 -T period time over which samples are considered (default 60 seconds)
54 -U units export observation values using the given units
55 -V units export counter values using the given units
57 Installing the "trace" Performance Metrics Domain Agent (PMDA) ...
59 Use the default installation [y]?
60 Trace period (in seconds) [60]?
61 Number of buckets [5]?
62 Port number for client connections [4323]?
63 The dimension and scale for the trace.observe.value metrics may be expressed
64 in terms of Space, Time and Count (i.e. events or messages). The default
65 dimension and scale is "None". Do you wish to accept the default dimension
67 The dimension is expressed in terms of powers of Space, Time and Count.
68 For example, bytes per second would be 1 -1 0, and milliseconds per message
70 Enter the dimension for Space, Time and Count [0 0 0]: Scale for the Space dimension is expressed as:
76 Enter the scale for the Space dimension [0]: -- Sorry, Space scale must be between 0 and 4 --
77 Scale for the Space dimension is expressed as:
83 Enter the scale for the Space dimension [0]: -- Sorry, Space scale must be between 0 and 4 --
84 Scale for the Space dimension is expressed as:
90 Enter the scale for the Space dimension [0]: Scale for the Time dimension is expressed as:
97 Enter the scale for the Time dimension: -- Sorry, Time scale must be between 0 and 5 --
98 Scale for the Time dimension is expressed as:
105 Enter the scale for the Time dimension: -- Sorry, Time scale must be numeric (not foo) --
106 Scale for the Time dimension is expressed as:
113 Enter the scale for the Time dimension:
114 Using the following units for trace.observe.value:
115 Dimensions: space=1 time=-1 count=0
116 Scale: space=0 time=3 count=0
119 The dimension and scale for the trace.counter.value metrics may be expressed
120 in terms of Space, Time and Count (i.e. events or messages). The default
121 dimension and scale is "None". Do you wish to accept the default dimension
123 Using the following units for trace.counter.value:
124 Dimensions: space=0 time=0 count=0
125 Scale: space=0 time=0 count=0
128 Client host access - (A)llow/(D)isallow [Enter to complete install]?
129 Updating the Performance Metrics Name Space (PMNS) ...
130 Terminate PMDA if already installed ...
131 [...install files, make output...]
132 Updating the PMCD control file, and notifying PMCD ...
133 Check trace metrics have appeared ... 20 metrics and 6 values
134 Note: some warnings are expected until trace API calls are made - refer to
135 the man pages for pmtrace(1) and pmdatrace(3) for further details.
138 Data Type: double InDom: 10.2 0x2800002
139 Semantics: instant Units: byte / sec
140 Installing the "trace" Performance Metrics Domain Agent (PMDA) ...
142 Use the default installation [y]?
143 Trace period (in seconds) [60]?
144 Number of buckets [5]?
145 Port number for client connections [4323]?
146 The dimension and scale for the trace.observe.value metrics may be expressed
147 in terms of Space, Time and Count (i.e. events or messages). The default
148 dimension and scale is "None". Do you wish to accept the default dimension
150 Using the following units for trace.observe.value:
151 Dimensions: space=0 time=0 count=0
152 Scale: space=0 time=0 count=0
155 The dimension and scale for the trace.counter.value metrics may be expressed
156 in terms of Space, Time and Count (i.e. events or messages). The default
157 dimension and scale is "None". Do you wish to accept the default dimension
159 The dimension is expressed in terms of powers of Space, Time and Count.
160 For example, bytes per second would be 1 -1 0, and milliseconds per message
162 Enter the dimension for Space, Time and Count [0 0 0]: Scale for the Space dimension is expressed as:
168 Enter the scale for the Space dimension [0]: Scale for the Time dimension is expressed as:
175 Enter the scale for the Time dimension: Scale for the Count dimension is expressed:
176 as a power of 10 (e.g. 6 for 10^6, or -3 for 10^-3) [0]: -- Sorry, Count scale must be numeric (not foo) --
177 Scale for the Count dimension is expressed:
178 as a power of 10 (e.g. 6 for 10^6, or -3 for 10^-3) [0]:
179 Using the following units for trace.counter.value:
180 Dimensions: space=1 time=-2 count=1
181 Scale: space=0 time=0 count=-4
184 Client host access - (A)llow/(D)isallow [Enter to complete install]?
185 Updating the Performance Metrics Name Space (PMNS) ...
186 Terminate PMDA if already installed ...
187 [...install files, make output...]
188 Updating the PMCD control file, and notifying PMCD ...
189 Check trace metrics have appeared ... 20 metrics and 6 values
190 Note: some warnings are expected until trace API calls are made - refer to
191 the man pages for pmtrace(1) and pmdatrace(3) for further details.
194 Data Type: double InDom: 10.3 0x2800003
195 Semantics: counter Units: byte count x 10^-4 / nanosec^2
196 Installing the "trace" Performance Metrics Domain Agent (PMDA) ...
198 Use the default installation [y]?
199 Trace period (in seconds) [60]?
200 Number of buckets [5]?
201 Port number for client connections [4323]?
202 The dimension and scale for the trace.observe.value metrics may be expressed
203 in terms of Space, Time and Count (i.e. events or messages). The default
204 dimension and scale is "None". Do you wish to accept the default dimension
206 Using the following units for trace.observe.value:
207 Dimensions: space=0 time=0 count=0
208 Scale: space=0 time=0 count=0
211 The dimension and scale for the trace.counter.value metrics may be expressed
212 in terms of Space, Time and Count (i.e. events or messages). The default
213 dimension and scale is "None". Do you wish to accept the default dimension
215 Using the following units for trace.counter.value:
216 Dimensions: space=0 time=0 count=0
217 Scale: space=0 time=0 count=0
220 Client host access - (A)llow/(D)isallow [Enter to complete install]?
221 Updating the Performance Metrics Name Space (PMNS) ...
222 Terminate PMDA if already installed ...
223 [...install files, make output...]
224 Updating the PMCD control file, and notifying PMCD ...
225 Check trace metrics have appeared ... 20 metrics and 6 values
226 Note: some warnings are expected until trace API calls are made - refer to
227 the man pages for pmtrace(1) and pmdatrace(3) for further details.
230 Data Type: double InDom: 10.2 0x2800002
231 Semantics: instant Units: none
234 Data Type: double InDom: 10.3 0x2800003
235 Semantics: counter Units: none