From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] 9grid
Date: Tue, 11 Nov 2008 16:13:14 -0800 [thread overview]
Message-ID: <13426df10811111613u4ed6c6a4n8e0359905dfdbe94@mail.gmail.com> (raw)
In-Reply-To: <e4a48b24-5cd4-42e9-9072-16eeb34ac3e3@e38g2000prn.googlegroups.com>
On Tue, Nov 11, 2008 at 7:12 AM, <lupin636@gmail.com> wrote:
> Thanks john, i would like to send simple programs (jobs) to the nodes
> (diskless cpu server) of a 9grid from terminal, and get responses from
> them. How can i do it?
>
suppose you have a list of nodes
cpu% NODES=(a b c d)
cpu% echo $NODES
a b c d
cpu% for (i in $NODES) {
cpu -h $i -c some-command&
}
Go ahead. Try it!
for (i in $NODES) {
cpu -h $i -c date&
}
OK, now suppose you have what in the high end business is still called
an 'input deck'. It's in a weird place. You get to it by saying
some-command -i input-file
for (i in $NODES) {
cpu -h $i -c some-command -i your-file&
}
This will work whether there is a mount on those nodes for your home
directory or not. Comes free with cpu.
What if you for whatever reason want a ps to show all the proces on
all the nodes you're running on.
for (i in $NODES) {
import -a $i .com /proc /proc
}
Your /proc is now the unified /proc of all your nodes. (I used to do
this all the time with my plan 9 minicluster)
That way, if you want to kill all the some-commands running on ALL your nodes:
slay some-command | rc
The point being that you only need to run this command on the
front-end, not on each node.
You just can't even try to do this sort of thing with ssh.
ron
next prev parent reply other threads:[~2008-11-12 0:13 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 12:09 erik quanstrom
2008-11-11 13:18 ` lupin636
2008-11-11 14:42 ` john
2008-11-11 15:12 ` lupin636
2008-11-11 15:40 ` Uriel
2008-11-11 16:32 ` lupin636
2008-11-11 17:14 ` Uriel
2008-11-12 0:13 ` ron minnich [this message]
2008-11-12 0:11 ` erik quanstrom
2008-11-12 0:41 ` ron minnich
2008-11-12 0:36 ` erik quanstrom
2008-11-12 0:59 ` ron minnich
2008-11-12 10:27 ` lupin636
2008-11-12 14:38 ` john
2008-11-12 16:16 ` lupin636
2008-11-13 12:08 ` lupin636
2008-11-13 12:28 ` erik quanstrom
2008-11-13 15:32 ` lupin636
-- strict thread matches above, loose matches on Subject: below --
2008-11-17 14:14 erik quanstrom
2008-11-17 16:22 ` lupin636
2008-11-14 12:23 erik quanstrom
2008-11-14 15:10 ` lupin636
2008-11-17 10:12 ` lupin636
2008-11-17 11:54 ` erik quanstrom
2008-11-17 14:13 ` lupin636
2008-11-13 15:43 erik quanstrom
2008-11-13 17:06 ` lupin636
2008-11-13 17:24 ` andrey mirtchovski
2008-11-13 17:26 ` erik quanstrom
2008-11-14 9:44 ` lupin636
2008-11-14 9:44 ` torsbohn
2008-11-14 13:53 ` erik quanstrom
2008-11-10 18:38 erik quanstrom
2008-11-11 9:50 ` lupin636
2008-11-10 11:35 erik quanstrom
2008-11-10 14:13 ` lupin636
2008-11-10 17:35 ` lupin636
2008-11-10 17:46 ` ron minnich
2008-11-11 9:50 ` lupin636
2008-11-10 9:56 lupin636
2005-06-09 2:17 YAMANASHI Takeshi
2005-06-09 2:28 ` andrey mirtchovski
2005-06-09 1:41 andrey mirtchovski
2005-06-09 1:27 YAMANASHI Takeshi
2005-06-09 3:01 ` Ronald G. Minnich
2005-06-08 14:14 Steve Simon
2005-06-08 15:16 ` Russ Cox
2005-06-08 20:55 ` arisawa
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=13426df10811111613u4ed6c6a4n8e0359905dfdbe94@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=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).