Re: [foxboro] Solaris: rexec on second-Ethernet

  • From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Wed, 1 Aug 2007 07:54:49 -0400

/usr/local/rexec is a Foxboro written utility. =


Regards,

Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On=
 Behalf Of Mostafa mohamed
Sent: Wednesday, August 01, 2007 12:41 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Solaris: rexec on second-Ethernet

HI
rexec is a unix utility. it opens a port and a socket to the hostname you =

write.
what I beleive is that it is not possible through the second ethernet card =

as you can see from cshell that it sees the first NIC so can you try rlogin=
 =

on the same machine with the second ethernet name and try rexec.
I think rsh will not do the same as rexec will redirect the output to your =

screen other wise you have to redirect the output to a file then copy the =

file to the originated workstation



Mostafa





>From: Corey R Clingo <corey.clingo@xxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: foxboro@xxxxxxxxxxxxx
>Subject: Re: [foxboro] Solaris: rexec on second-Ethernet
>Date: Tue, 31 Jul 2007 10:15:23 -0500
>
>I tried "rexec otheraw 'ls /' " here.  According to snoop, it doesn't even=

>send out any IP traffic (nor does it give any output from the ls).  I
>would therefore have to second Alex's recommendation to use rsh instead,
>or other roll-yer-own alternatives like ssh.  rexec lives in /usr/local,
>so I guess it is some sort of Foxboro utility and not the standard one
>from Unix.ls /sbin/r*
>
>IP traffic will flow over the second ethernet if you use an IP address on
>the second ethernet as a target.  We define an additional set of
>hostnames, like 01aw23a, 02aw13a for AWs 01AW23 and 02AW13, respectively.
>These hostnames map to IP addresses on a different network from the
>nodebus, e.g., 172.16.1.23, 172.16.1.13, either in every machine's
>/etc/hosts or in DNS.
>
>
>We can then do "rsh 01aw23a" from 02AW13 and it will go over the second
>ethernet rather than the nodebus.
>
>
>Corey Clingo
>BASF Corporation
>
>
>
>
>
>
>"Hegewisch, Dirk" <Dirk.Hegewisch@xxxxxxxxxxxx>
>Sent by: foxboro-bounce@xxxxxxxxxxxxx
>07/30/2007 07:13 AM
>Please respond to
>foxboro@xxxxxxxxxxxxx
>
>
>To
><foxboro@xxxxxxxxxxxxx>
>cc
>
>Subject
>[foxboro] Solaris: rexec on second-Ethernet
>
>
>
>
>
>Hi list.
>
>In some scripts we are using rexec on our AWs.
>
>Unfortunately does the Foxboro rexec only use the Nodebus (first Ethernet
>connection)
>
>Another Problem is that the Foxboro rexec requires an X-Client (Port 6000)=

>to work with "normal" Speed ...
>A simple "rexec AWLBUG /bin/ls" took nearly one Minute (If you don't
>believe - try it)
>
>Now we are looking for a solution to use rexec on the second-Ethernet.
>
>VSM21U# which rexec
>/usr/local/rexec
>VSM21U# what /usr/local/rexec
>/usr/local/rexec:
>dsserver.c      7.2 Foxboro Company 8/15/90
>sf_server.c     1.1 50 Series I/A, Foxboro Company 9/24/91
>dsamap.c        2.1 vc
>iserve.c        7.2 I/A , Foxboro Co. 8/15/90
>....
>
>How can we use the original Solaris rexec?  Any Ideas?
>
>Regards
>Dirk Hegewisch
>__________________________________________________________
>INEOS K=F6ln GmbH
>
>
>
>
>_______________________________________________________________________
>This mailing list is neither sponsored nor endorsed by Invensys Process
>Systems (formerly The Foxboro Company). Use the info you obtain here at
>your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
>foxboro mailing list:             //www.freelists.org/list/foxboro
>to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
>to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
>
>
>
>_______________________________________________________________________
>This mailing list is neither sponsored nor endorsed by Invensys Process
>Systems (formerly The Foxboro Company). Use the info you obtain here at
>your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
>foxboro mailing list:             //www.freelists.org/list/foxboro
>to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
>to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>

_________________________________________________________________
http://newlivehotmail.com

 =

 =

_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 =

foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
 =




Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
 not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: