On 11/9/07, Steve Simon <[EMAIL PROTECTED]> wrote: // was there ever any thought that cpu could/should put you // onto the least loaded machine in your authdom...
That seems more a server function than a client function to me; thus, cpu(1) would be the wrong place to do it. I'd rather the servers in some cluster figure out amongst themselves who handles a given call, rather than the client having to do some sort of polling or inquiry. Also, that keeps a more consistent user experience. // ...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. Certainly originally cpu(1) was frequently used simply to get to a bigger machine. That's the way many of the early docs describe its use, and was also the practice at the Labs a decade ago. This use has become less common (at least for me) as terminals become so much more powerful. Wanting to get at particular resources is also a valid reason, of course, although in my usage import and friends more often serve that need. // why does cpu not have a default argument? I'm not sure I follow what you're asking for here. $cpu *is* the default; if you want something else, you can give it. Anthony
