rlogin(1C) rlogin(1C) NAME rlogin - remote login SYNOPSIS rlogin rhost [ -l username ] [ -ec ] [ -L ] [ -8 ] [-4 | -6] rlogin username@rhost [ -ec ] [ -L ] [ -8 ] [-4 | -6] DESCRIPTION rlogin connects your terminal on the current local host system to the remote host system rhost. The remote username used is the same as your local username, unless you specify a different remote name with the -l option or use the username@rhost format. The rlogin arguments and options are: rhost The hostname of the remote system. username The user ID to be used on the remote system. -l username Specifies the user ID to be used on the remote system. -ec Specifies a different escape character. There is no space separating this option flag and the argument character, c. -L Allows the rlogin session to be run in litout mode. A line of the form ~. disconnects from the remote host, where ~ is the escape character. A line starting with ~! starts a shell on the IRIS. Similarly, the line ~^Z (where ^Z, <Ctrl-z>, is the suspend character) suspends the rlogin session if you are using csh(1). -8 Allows an 8-bit input data path at all times; otherwise parity bits are stripped except when the remote side's stop and start characters are other than ^S/^Q. -4 Use IPv4 addresses only. -6 Use IPv6 addresses only. Each host has a file /etc/hosts.equiv that contains a list of remote hosts (equivalent hosts) with which it shares account names. The hostnames must be the standard names as described in rsh(1C). When you rlogin as the same user on an equivalent host, you do not need to give a password. Each user can also have a private equivalence list in a file .rhosts in his home directory. Each line in this file should contain an rhost and a username separated by a space, which gives an additional remote host where logins without passwords are permitted. If the originating user is not equivalent to the remote user, the remote host prompts for a login and password as in login(1). To avoid some security problems, the .rhosts file must be owned by either the remote user or root. Under Trusted IRIX/CMW, only the first field of the /etc/hosts.equiv and $HOME/.rhosts files is relevant to the system. The second field is ignored as a comment. This behavior places a restriction on the rsh and rlogin programs, which do not allow unchallenged access (access without demanding a password) unless the remote user name and user ID are exactly identical to the local user name and user ID. If a different name or user ID is used, the user is prompted for a password that authenticates the user's identity in the usual manner. The user will also be prompted for a password if the MAC label of the login session does not dominate the MAC label of the $HOME/.rhosts file. It is recommended that the $HOME/.rhosts file be labeled such that it is dominated by all other labels that the user can login with. The remote terminal type is the same as your local terminal type (as given in your TERM environment variable). The TERM value iris-ansi is converted to iris-ansi-net when sent to the host. The terminal or window size is also copied to the remote system if the server supports the option, and changes in size are reflected as well. All echoing takes place at the remote site, so that (except for delays) the rlogin is transparent. Flow control via ^S and ^Q and flushing of input and output on interrupts are handled properly. NOTES In a Trusted IRIX environment, a user can rlogin at a different MAC label (see dominance(5)) and/or capability set (see capability(4)) by specifying the label and capability set after the username at the login prompt. See login(1) for more details. However, the label and capability set can not be specified using command line options. SEE ALSO login(1), rsh(1C), capability(4) hosts(4), rhosts(4). dominance(5) BUGS Only the TERM environment variable is propagated. The rlogin protocol should be extended to propagate useful variables, such as DISPLAY. (Note that telnet(1C) is able to propagate environment variables.) Page 2