Re: [foxboro] Solaris: rexec on second-Ethernet
- From: "Mostafa mohamed" <mostafa_atatork@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 30 Jul 2007 13:23:43 +0000
Did you use the dns name that corresponds to the second ethernet card in the
hosts file
Mostafa
>From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: <foxboro@xxxxxxxxxxxxx>
>Subject: Re: [foxboro] Solaris: rexec on second-Ethernet Date: Mon, 30 Jul
>2007 08:34:08 -0400
>
>Try rsh. Not the restricted shell, but the remote shell.
>
>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 Hegewisch, Dirk
>Sent: Monday, July 30, 2007 7:14 AM
>To: foxboro@xxxxxxxxxxxxx
>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
>c=
>onnection)
> =
>
>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
>believ=
>e - 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
> =
>
>
>
>
>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
>
_________________________________________________________________
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507
_______________________________________________________________________
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:
