rlogin starts a terminal session on the remote host specified as host. The remote host must be running a rlogind service (or daemon) for rlogin to connect to.
rlogin uses the standard rhosts authorization mechanism.
When no user name is specified either with the
rlogin actually sends two user names to the rlogind service (or daemon): remuser and locuser.
remuser is your user name that you are currently logged into the client machine as (and includes either your domain or machine name). It is called remuser by the service (or daemon) because from the point of view of the service (or daemon), the client machine is remote. remuser is the name that must appear in either the global hosts.equiv file or the appropriate .rhosts file on the server. remuser cannot be set by the user.
locuser is the user name that the service (or daemon) uses to execute the command on the server. Again, it is named as such, because from the point of view of the service (or daemon), the server is the local machine. This is either the user name that you are currently logged in as (minus any domain information if you are a domain user) or the user name explicitly entered on the rlogin command line.
When using rlogin. a line of the form
(where esc_char is the escape character) disconnects from the remote host. By default, the escape character is the tilde (~).
All echoing takes place at the remote site, so that (except for delays) the remote login is transparent. Flow control via ^S/^Q and flushing of input and output on interrupts are handled properly.
Because the rsh and rcp utilities resend the current without the domain if it is too long and the rlogin utility does not, a user may require two entries in the hosts.equiv or .rhosts file. If the full name (including domain) is too long for the rshd service (or daemon) being used, the user needs one entry with the full user name (including domain) for use with rlogind and a second with the the same user name minus the domain for use with rshd.
enables socket debugging on the TCP sockets used for communication with the remote host. This option also displays the locuser and remuser being sent to rlogind. This can be useful for determining the exact case of your domain (or machine) and user names, which must be correct in the .rhosts and hosts.equiv files.
stops any character from being recognized as an escape character.
specifies the character to be used as the escape character. This specification may be as a literal character, or as an octal value in the form \nnn. Without this option, the escape character defaults to the tilde (~).
specifies an alternate user name for the remote login. If you do not specify either this option or a username@host argument, your local user name is used.
specifies the terminal type. Only two terminal types are currently supported: dumb and ansi. The default is ansi.
An operation was attempted on something that is not a socket
Possible exit status values are:
This product includes software developed by the University of California, Berkeley and its contributors.
All UNIX systems. Windows 7. Windows Server 2008 R2. Windows 8. Windows Server 2012. Windows 10. Windows Server 2016.
Most versions of rlogind have a limit to the length of user name they can handle. As a result, you may receive an error message stating that either remuser or locuser is too long.
When remuser is too long, you need a shorter user name on the client machine (if you are a domain user, remember that the domain information is included in remuser).
When the "locuser is too long" error is received, it means that not only is the locuser name longer than the server's limit, but, by extension, it is an invalid user name on that server.
PTC MKS Toolkit for System Administrators
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition
MKS Toolkit Connectivity Solutions Guide
PTC MKS Toolkit 10.1 patch 1 Documentation Build 2.