From: lupin636@gmail.com
To: 9fans@9fans.net
Subject: Re: [9fans] 9grid
Date: Mon, 10 Nov 2008 17:35:32 +0000 [thread overview]
Message-ID: <10c20060-1038-4909-80d9-f7cea4be23cc@v22g2000pro.googlegroups.com> (raw)
In-Reply-To: <c09394dd43f3d4c6b7a9280f26af6d47@quanstro.net>
I have a doubt.....because i was thinking about all i have to do, and
i don't know if using cpu command is the right thing to do. anyway,
the fact is, i have to launch a simple task from terminal (connected
by armando) to a node on the cluster (diskless cpu server), i thought
that cpu command was right but i'm not really sure anymore, because in
unix i used to use "rsh" and "rcmd".
any suggestions please??
thanks in advance to all of you,
bye,
Armando.
On 10 Nov, 15:13, lupin...@gmail.com wrote:
> Thanks for replaying...
> Sorry but i got confusion about your replay, i think i don't
> understand very well
> I want to make it clear first that the file/auth server are the same
> pc, and the cpuservers are the nodes of the cluster (5 nodes), which
> are diskless, and a terminal (my laptop).
> I'd like to use the cpu(1) command to connect to one node of the
> cluster (cpuserver) from the terminal, i tried by doing:
>
> term% cpu -h cpus
> term% ls /mnt/term
> term%
>
> but i think it isn't correct, because the prompt is still term%, and /
> mnt/term is empty, i did "ls /mnt/term" because i wanted to see if the
> namespace was mounted.
> is that correct?
> I hope i explain to you in the right way.
> thanks again..
>
> bye,
>
> Armando
next prev parent reply other threads:[~2008-11-10 17:35 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 11:35 erik quanstrom
2008-11-10 14:13 ` lupin636
2008-11-10 17:35 ` lupin636 [this message]
2008-11-10 17:46 ` ron minnich
2008-11-11 9:50 ` 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-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
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
2008-11-10 18:38 erik quanstrom
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=10c20060-1038-4909-80d9-f7cea4be23cc@v22g2000pro.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).