From: lupin636@gmail.com
To: 9fans@9fans.net
Subject: Re: [9fans] 9grid
Date: Tue, 11 Nov 2008 15:12:44 +0000 [thread overview]
Message-ID: <e4a48b24-5cd4-42e9-9072-16eeb34ac3e3@e38g2000prn.googlegroups.com> (raw)
In-Reply-To: <d0a99c33-501b-4b57-8a31-c27115ec7ec4@l33g2000pri.googlegroups.com>
On 11 Nov, 15:46, j...@csplan9.rit.edu wrote:
> > Ok, i just ran some local �commands from cpu server, and it is ok, i'm
> > gonna use the cpu servers only like a compute nodes. From cpu server i
> > wanted to see responses , so �i did and got this:
> > � � � � cpus# ssh terminal name
> > � � � � ssh: dialing terminal name: connection refused
> > � � � � cpus# ssh file server name
> > � � � � ssh: reading server version: unexpected EOF
> > the second error, i got also when i tried either from terminal or file
> > server.
> > yes, bootes is the cpu server's hostowner,but on terminal i log as
> > Armando.
> > what do you mean with "configuration error"?where could it be?
> > is ssh right to launch a task from terminal?
>
> > thanks again
>
> > Armando
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?
> You want to be sitting at a terminal, and start a command on a cpu
> server, right?
>
> cpu -h <cpuserver> -c <command> <args>
>
> That will execute the command on the cpu server and leave you at the
> terminal prompt when you are done.
>
> I have no idea why you are trying to ssh from your cpu server to your
> terminal or to the fileserver. �Forget ssh. �If you have a Plan 9
> network, ssh is 100% wrong for you.
>
> John
next prev parent reply other threads:[~2008-11-11 15:12 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 [this message]
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
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=e4a48b24-5cd4-42e9-9072-16eeb34ac3e3@e38g2000prn.googlegroups.com \
--to=lupin636@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).