iX 6.5)

78 Chapter6

REMSH Service

Conﬁguring remsh Client

UNIX Conﬁguration

The remsh service does not prompt for user ID and passwords. That

information is handled via the command line parameters and

conﬁguration 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 in the remote

user’s home directory or by use of the ﬁle /etc/hosts.equiv. See the

man pages of the UNIX system for details on how to set up a

/etc/hosts.equiv ﬁle. A user’s .rhosts ﬁle entry will consist of the

MPE/iX system name and user ID.

If you wish to access the HP-UX Host “taltos” as user cawti from the

MPE/iX system jhereg while user MANAGER.SYS, you’ll need to set up a

host equivalency via the /etc/hosts.equiv ﬁle, or you will create a

.rhosts ﬁle in the home directory of user cawti on the “taltos”

machine. The .rhosts ﬁle entry would look like:

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 ﬁle 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

uppercase.