From: Boyd Roberts boyd@france3.fr
Subject: "cpu" command, other related stuff
Date: Mon, 26 Aug 1996 10:39:15 +0200 [thread overview]
Message-ID: <19960826083915.jZlJA0KDkcET1xSwoH2L8dX5CdIxlM0E9t0jHi5BaG0@z> (raw)
From: Photon <photon@nol.net>
Have a list of cpu servers stored in some variable (i.e. $cpus), and have
the cpu command remotely check the load average of each cpu server in the
list, and pick the one with the lowest load average. This would allow for
better balancing of jobs in a large multi-cpuserver, multi-user
environment.
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.
next reply other threads:[~1996-08-26 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-26 8:39 Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-08-27 7:07 Nigel
1996-08-25 22:45 Photon
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=19960826083915.jZlJA0KDkcET1xSwoH2L8dX5CdIxlM0E9t0jHi5BaG0@z \
--to=9fans@9fans.net \
/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).