Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

Chapter 10 211
Technical Articles
The REMSH Client Functionality
To edit the services file:
1. You may edit the SERVICES.NET.SYS file from MPE/iX. Open the
services file with a text editor.
2. Verify that the following line exists in the file.
shell 514/tcp cmd # remote command, no passwd used
a. Add the line if it does not exist.
b. If the line already exists in the file and is preceded by a pound
symbol (#), delete the # and any spaces before the service name to
enable the service.
3. Save the file and exit the editor program.
UNIX Configuration
The REMSH service does not prompt for user ID and passwords. That
information is handled via the command line parameters and
configuration on the UNIX host. See the using REMSH section for
details on how the user id is determined and passed to the UNIX host.
Password information is bypassed by use of a .rhosts file in the remote
user's home directory or by use of the file /etc/hosts.equiv. See the man
pages of the UNIX system for details on how to set up a /etc/hosts.equiv
file. A user's .rhosts file entry will consist of the MPE/iX system name
and user id.
For example, to access the HP-UX system “taltos” as user “cawti,” from
the MPE/iX system “jhereg” while user MANAGER.SYS, set up a host
equivalency via the /etc/hosts.equiv file, or you will create a .rhosts file
in the home directory of user “cawti” on the “taltos” machine. The
.rhosts file would look like this:
jhereg MANAGER.SYS
This will cause the REMSH daemon on the UNIX host to allow a
connection from MANAGER.SYS on “jhereg” to the “cawti” user on the
host “taltos.” The .rhosts file for user “cawti” would contain an entry for
every host and userid that you desired to access the “taltos” host as if
they were the user “cawti.”
NOTE The MPE/iX equivalent of the UNIX user id is the User.Account. An
artifact of the MPE/iX implementation is that the MPE/iX information
is usually reported in upper case. So be sure your .rhosts or
/etc/hosts.equiv entries use the MPE/iX user ID information in upper
case.