From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 27 Aug 1996 08:07:09 +0100
From: Nigel Roles ngr@symbionics.co.uk
Subject: "cpu" command, other related stuff
Topicbox-Message-UUID: 4c056046-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19960827070709.1x5m52wLa9fCCOe0G1Dtc3JRipXmCTz-G2SBzYtSe1k@z>

> if you really wanted to do this, i wouldn't break cpu.  i'd write findcpu:
>
>    cpu -h `{findcpu}
>
> or you could use it to set $cpu at login.
>
> i think cpu was intended to be used with a particular cpu server, not
> just one with a low 'load average' [a totally foreign concept to plan
> 9].  the choice being based on a particular function that cpu fulfills.
>
Also, making the decision once at the start is about as much use as a
chocolate teapot, since you might well stay connected to a CPU server
for days. In a 'real' system you might wish to choose the cpu
with the fast link to the fileserver where your files live.


Nigel Roles