| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 630.1 | | DECWET::ONO | Software doesn't break-it comes broken | Mon Apr 28 1997 09:43 | 15 |
| The CPU field is supposed to reflect the number of CPUs in the
client system. Some clients report this back to the NetWorker
server, some do not.
If you change the value in this field for a self-identifying
client, then the server will set the field back to the value
reported by the client.
If you change the value in this field for a non-identifying
client, you can sometimes end up with "CPU attribute does not
match" errors.
What is it that you want to do with the CPU field?
Wes
|
| 630.2 | | EVTAI1::POUSSARD | | Tue Apr 29 1997 03:08 | 4 |
| Just to say that some clients are multiprocessor clients and
customer wanted to know what was the correlation between this field and
the multiprocessor system ans the impact
|
| 630.3 | | DECWET::ONO | Software doesn't break-it comes broken | Tue Apr 29 1997 10:27 | 7 |
| If the client software reports the number of CPUs, then this
field will be set. Otherwise, it will probably stay at 1.
I think this field is just used for a sanity check at save start
time.
Wes
|
| 630.4 | | DECWET::FARLEE | Insufficient Virtual um...er.... | Tue Apr 29 1997 11:28 | 5 |
| Actually, the only practical impact of this field is that it is used as
part of the algorithm to determine which clients are cluster hosts
and which are cluster services. Cluster services report themselves
as having 0 CPUs. Any non-0 value is the same as far as licensing
is concerned.
|