/var/lib/pcp/testsuite/602.out is in pcp-testsuite 3.9.10.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 | QA output created by 602
--- Usage message ---
Usage: pmdatrace [options]
Options:
-d domain use domain (numeric) for metrics domain of PMDA
-l logfile write log into logfile rather than using default file
-A access host based access control
-I port expect programs to connect on given inet port (number/name)
-N buckets number of historical data buffers maintained
-T period time over which samples are considered (default 60 seconds)
-U units export observation values using the given units
-V units export counter values using the given units
--- Bad units specification #1 ---
pmdatrace: token parse error in string "1,1,1"
Usage: pmdatrace [options]
Options:
-d domain use domain (numeric) for metrics domain of PMDA
-l logfile write log into logfile rather than using default file
-A access host based access control
-I port expect programs to connect on given inet port (number/name)
-N buckets number of historical data buffers maintained
-T period time over which samples are considered (default 60 seconds)
-U units export observation values using the given units
-V units export counter values using the given units
--- Bad units specification #2 ---
pmdatrace: token parse error in string "1,,1,1,1,1"
Usage: pmdatrace [options]
Options:
-d domain use domain (numeric) for metrics domain of PMDA
-l logfile write log into logfile rather than using default file
-A access host based access control
-I port expect programs to connect on given inet port (number/name)
-N buckets number of historical data buffers maintained
-T period time over which samples are considered (default 60 seconds)
-U units export observation values using the given units
-V units export counter values using the given units
--- Bad units specification #3 ---
pmdatrace: integer parse error for substring "foo"
Usage: pmdatrace [options]
Options:
-d domain use domain (numeric) for metrics domain of PMDA
-l logfile write log into logfile rather than using default file
-A access host based access control
-I port expect programs to connect on given inet port (number/name)
-N buckets number of historical data buffers maintained
-T period time over which samples are considered (default 60 seconds)
-U units export observation values using the given units
-V units export counter values using the given units
Installing the "trace" Performance Metrics Domain Agent (PMDA) ...
Use the default installation [y]?
Trace period (in seconds) [60]?
Number of buckets [5]?
Port number for client connections [4323]?
The dimension and scale for the trace.observe.value metrics may be expressed
in terms of Space, Time and Count (i.e. events or messages). The default
dimension and scale is "None". Do you wish to accept the default dimension
and scale [y]?
The dimension is expressed in terms of powers of Space, Time and Count.
For example, bytes per second would be 1 -1 0, and milliseconds per message
would be 0 1 -1.
Enter the dimension for Space, Time and Count [0 0 0]: Scale for the Space dimension is expressed as:
0 (bytes)
1 (kilobytes)
2 (megabytes)
3 (gigabytes)
4 (terabytes)
Enter the scale for the Space dimension [0]: -- Sorry, Space scale must be between 0 and 4 --
Scale for the Space dimension is expressed as:
0 (bytes)
1 (kilobytes)
2 (megabytes)
3 (gigabytes)
4 (terabytes)
Enter the scale for the Space dimension [0]: -- Sorry, Space scale must be between 0 and 4 --
Scale for the Space dimension is expressed as:
0 (bytes)
1 (kilobytes)
2 (megabytes)
3 (gigabytes)
4 (terabytes)
Enter the scale for the Space dimension [0]: Scale for the Time dimension is expressed as:
0 (nanoseconds)
1 (microseconds)
2 (milliseconds)
3 (seconds)
4 (minutes)
5 (hours)
Enter the scale for the Time dimension: -- Sorry, Time scale must be between 0 and 5 --
Scale for the Time dimension is expressed as:
0 (nanoseconds)
1 (microseconds)
2 (milliseconds)
3 (seconds)
4 (minutes)
5 (hours)
Enter the scale for the Time dimension: -- Sorry, Time scale must be numeric (not foo) --
Scale for the Time dimension is expressed as:
0 (nanoseconds)
1 (microseconds)
2 (milliseconds)
3 (seconds)
4 (minutes)
5 (hours)
Enter the scale for the Time dimension:
Using the following units for trace.observe.value:
Dimensions: space=1 time=-1 count=0
Scale: space=0 time=3 count=0
The dimension and scale for the trace.counter.value metrics may be expressed
in terms of Space, Time and Count (i.e. events or messages). The default
dimension and scale is "None". Do you wish to accept the default dimension
and scale [y]?
Using the following units for trace.counter.value:
Dimensions: space=0 time=0 count=0
Scale: space=0 time=0 count=0
Client host access - (A)llow/(D)isallow [Enter to complete install]?
Updating the Performance Metrics Name Space (PMNS) ...
Terminate PMDA if already installed ...
[...install files, make output...]
Updating the PMCD control file, and notifying PMCD ...
Check trace metrics have appeared ... 20 metrics and 6 values
Note: some warnings are expected until trace API calls are made - refer to
the man pages for pmtrace(1) and pmdatrace(3) for further details.
trace.observe.value
Data Type: double InDom: 10.2 0x2800002
Semantics: instant Units: byte / sec
Installing the "trace" Performance Metrics Domain Agent (PMDA) ...
Use the default installation [y]?
Trace period (in seconds) [60]?
Number of buckets [5]?
Port number for client connections [4323]?
The dimension and scale for the trace.observe.value metrics may be expressed
in terms of Space, Time and Count (i.e. events or messages). The default
dimension and scale is "None". Do you wish to accept the default dimension
and scale [y]?
Using the following units for trace.observe.value:
Dimensions: space=0 time=0 count=0
Scale: space=0 time=0 count=0
The dimension and scale for the trace.counter.value metrics may be expressed
in terms of Space, Time and Count (i.e. events or messages). The default
dimension and scale is "None". Do you wish to accept the default dimension
and scale [y]?
The dimension is expressed in terms of powers of Space, Time and Count.
For example, bytes per second would be 1 -1 0, and milliseconds per message
would be 0 1 -1.
Enter the dimension for Space, Time and Count [0 0 0]: Scale for the Space dimension is expressed as:
0 (bytes)
1 (kilobytes)
2 (megabytes)
3 (gigabytes)
4 (terabytes)
Enter the scale for the Space dimension [0]: Scale for the Time dimension is expressed as:
0 (nanoseconds)
1 (microseconds)
2 (milliseconds)
3 (seconds)
4 (minutes)
5 (hours)
Enter the scale for the Time dimension: Scale for the Count dimension is expressed:
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) --
Scale for the Count dimension is expressed:
as a power of 10 (e.g. 6 for 10^6, or -3 for 10^-3) [0]:
Using the following units for trace.counter.value:
Dimensions: space=1 time=-2 count=1
Scale: space=0 time=0 count=-4
Client host access - (A)llow/(D)isallow [Enter to complete install]?
Updating the Performance Metrics Name Space (PMNS) ...
Terminate PMDA if already installed ...
[...install files, make output...]
Updating the PMCD control file, and notifying PMCD ...
Check trace metrics have appeared ... 20 metrics and 6 values
Note: some warnings are expected until trace API calls are made - refer to
the man pages for pmtrace(1) and pmdatrace(3) for further details.
trace.counter.value
Data Type: double InDom: 10.3 0x2800003
Semantics: counter Units: byte count x 10^-4 / nanosec^2
Installing the "trace" Performance Metrics Domain Agent (PMDA) ...
Use the default installation [y]?
Trace period (in seconds) [60]?
Number of buckets [5]?
Port number for client connections [4323]?
The dimension and scale for the trace.observe.value metrics may be expressed
in terms of Space, Time and Count (i.e. events or messages). The default
dimension and scale is "None". Do you wish to accept the default dimension
and scale [y]?
Using the following units for trace.observe.value:
Dimensions: space=0 time=0 count=0
Scale: space=0 time=0 count=0
The dimension and scale for the trace.counter.value metrics may be expressed
in terms of Space, Time and Count (i.e. events or messages). The default
dimension and scale is "None". Do you wish to accept the default dimension
and scale [y]?
Using the following units for trace.counter.value:
Dimensions: space=0 time=0 count=0
Scale: space=0 time=0 count=0
Client host access - (A)llow/(D)isallow [Enter to complete install]?
Updating the Performance Metrics Name Space (PMNS) ...
Terminate PMDA if already installed ...
[...install files, make output...]
Updating the PMCD control file, and notifying PMCD ...
Check trace metrics have appeared ... 20 metrics and 6 values
Note: some warnings are expected until trace API calls are made - refer to
the man pages for pmtrace(1) and pmdatrace(3) for further details.
trace.observe.value
Data Type: double InDom: 10.2 0x2800002
Semantics: instant Units: none
trace.counter.value
Data Type: double InDom: 10.3 0x2800003
Semantics: counter Units: none
|