What’s the easiest way to set up remote shell access over qnet?
Thanks,
Dan
I don’t think you can. Remote spanning isn’t support at this time.
QSSL please correct me if i’m wrong…
However you could probably redirect a local shell input output over
qnet " sh </net/machine/dev/con1 >/net/machine/dev/con1"
“Dan Helmick” <danielhelmick@earthlink.net> wrote in message
news:985vet$cnr$1@inn.qnx.com…
What’s the easiest way to set up remote shell access over qnet?
Thanks,
Dan
It seems you should be able to. The “on” utiltiy is shipped with RtP,
and it does have an option for spawning on a remote node. Unfortunately,
I don’t have two RtP systems up yet in order to check this out, although
I did try “on -n localhost sh” and that worked. I would assume that
“on -n <name_of_other_host> sh” would work, since I see no documentation
to the contrary (i.e. “on -n” saying “not currently implemented” or
somesuch).
-----Original Message-----
From: mcharest@modemcable124.132-200-24.mtl.mc.videotron.ca
[mailto:mcharest@modemcable124.132-200-24.mtl.mc.videotron.ca]On Behalf
Of Mario Charest
Posted At: Friday, March 09, 2001 7:34 PM
Posted To: newuser
Conversation: remote shell over qnet
Subject: Re: remote shell over qnet
I don’t think you can. Remote spanning isn’t support at this time.
QSSL please correct me if i’m wrong…
However you could probably redirect a local shell input output over
qnet " sh </net/machine/dev/con1 >/net/machine/dev/con1"
“Dan Helmick” <danielhelmick@earthlink.net> wrote in message
news:985vet$cnr$1@inn.qnx.com…
What’s the easiest way to set up remote shell access over qnet?
Thanks,
Dan
Rennie Allen <RAllen@csical.com> wrote:
: It seems you should be able to. The “on” utiltiy is shipped with RtP,
: and it does have an option for spawning on a remote node. Unfortunately,
: I don’t have two RtP systems up yet in order to check this out, although
: I did try “on -n localhost sh” and that worked. I would assume that
: “on -n <name_of_other_host> sh” would work, since I see no documentation
: to the contrary (i.e. “on -n” saying “not currently implemented” or
: somesuch).
on -n is not supported yet with qnet.
You will get the following if you try:
on -n ls
on: Must be done on local machine (ls)
I don’t have an ETA for when this will be available.
Peter
: -----Original Message-----
: From: mcharest@modemcable124.132-200-24.mtl.mc.videotron.ca
: [mailto:mcharest@modemcable124.132-200-24.mtl.mc.videotron.ca]On Behalf
: Of Mario Charest
: Posted At: Friday, March 09, 2001 7:34 PM
: Posted To: newuser
: Conversation: remote shell over qnet
: Subject: Re: remote shell over qnet
: I don’t think you can. Remote spanning isn’t support at this time.
: QSSL please correct me if i’m wrong…
: However you could probably redirect a local shell input output over
: qnet " sh </net/machine/dev/con1 >/net/machine/dev/con1"
: “Dan Helmick” <danielhelmick@earthlink.net> wrote in message
: news:985vet$cnr$1@inn.qnx.com…
:> What’s the easiest way to set up remote shell access over qnet?
:>
:> Thanks,
:> Dan
:>
:>
Peter Martin <peterm@qnx.com> wrote:
: Rennie Allen <RAllen@csical.com> wrote:
: : It seems you should be able to. The “on” utiltiy is shipped with RtP,
: : and it does have an option for spawning on a remote node. Unfortunately,
: : I don’t have two RtP systems up yet in order to check this out, although
: : I did try “on -n localhost sh” and that worked. I would assume that
: : “on -n <name_of_other_host> sh” would work, since I see no documentation
: : to the contrary (i.e. “on -n” saying “not currently implemented” or
: : somesuch).
: on -n is not supported yet with qnet.
: You will get the following if you try:
: on -n ls
: on: Must be done on local machine (ls)
Which is why the -n option isn’t documented. Too bad it’s in the usage
message.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
Which is why the -n option isn’t documented. Too bad it’s in the usage
message.
You mean there is other documentation besides the use message 
ps: that’s a joke Steve. The on-line documentation is very good, and
I use it frequently.
Rennie
The best documentation to find out what options are available for any
program is to use strings on it. Then you just look for a string of letters
seperated by colons. As for what all of those undocumentated options do,
they must all be obvious or the progrmmer wouldn’t have put them in there.
–
Bill Caroselli - Sattel Global Networks
1-818-709-6201 ext 122
“Rennie Allen” <RAllen@csical.com> wrote in message
news:D4907B331846D31198090050046F80C9033AE5@exchangecal.hq.csical.com…
Which is why the -n option isn’t documented. Too bad it’s in the usage
message.You mean there is other documentation besides the use message >
ps: that’s a joke Steve. The on-line documentation is very good, and
I use it frequently.Rennie