From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu(1) design...
Date: Fri, 9 Nov 2007 12:50:35 +0000 [thread overview]
Message-ID: <691e7ca02963cc4348bfb160ec4357de@quintile.net> (raw)
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
next reply other threads:[~2007-11-09 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 12:50 Steve Simon [this message]
2007-11-09 14:40 ` Anthony Sorace
2007-11-09 14:45 ` roger peppe
2007-11-09 14:55 ` Anthony Sorace
2007-11-09 15:33 ` Steve Simon
2007-11-09 15:46 ` ron minnich
2007-11-09 15:57 ` erik quanstrom
2007-11-09 14:52 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=691e7ca02963cc4348bfb160ec4357de@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).