From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <691e7ca02963cc4348bfb160ec4357de@quintile.net> From: "Steve Simon" Date: Fri, 9 Nov 2007 12:50:35 +0000 To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: [9fans] cpu(1) design... Topicbox-Message-UUID: f0332a40-ead2-11e9-9d60-3106f5b1d025 Trivial questions about cpu(1). was there ever any thought that cpu could/should put you onto the least loaded machine in your authdom (or an option to do this) or is this breaking the one tool does one job principal? If so has anyone ever done this (not difficult) or is the idea that you would only want to cpu(1) to another machine because of the services or network topology you (as a human) want rather than just to find more grunt. seccondly - why does cpu not have a default argument? this constantly irritates me, I often cpu as a different user, to run a command and go to a machine other than that defined by /env/cpu but no matter which I want I always need to flag the argument. just idle curiosity, its Friday after all. -Steve