HP-UX Reference (11i v2 03/08) - 1M System Administration Commands N-Z (vol 4)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

211

212

213

214

215

216

217

218

219

220

rlogind(1M) rlogind(1M)

International Code Set Support

Single- and multibyte character code sets are supported.

DIAGNOSTICS

Errors in establishing a connection cause an error message to be returned with a leading byte of 1

through the socket connection, after which the network connection is closed. Any errors generated by the

fork: No more processes

The server was unable to fork a process to handle the incoming connection.

Next step : Wait a period of time and try again. If this message persists, the server’s host may

have runaway processes that are using all the entries in the process table.

Cannot allocate pty on remote host

The server was unable to obtain a pseudo-terminal for use with the login process. Either all

pseudo-terminals were in use, or the pty driver has not been properly set up. Note that the

number of slave devices that can be allocated depends on NSTRPTY, a kernel tunable parame-

ter. This can be changed via SAM ( see ptm(7), pts(7)).

Next step: Check the pty conﬁguration of the host where

rlogind executes.

Permission denied

The server denied access because the client was not using a reserved port. This should only

happen to interlopers trying to break into the system.

/usr/bin/login: ...

The login program could not be started via exec(2) for the reason indicated.

Next step: Try to correct the condition causing the problem. If this message persists, contact

your system administrator.

rcmd: connect : <hostname>: Connection refused.

This generic message could be due to a number of reasons. One of the reasons could be because

the entry for login service is not present in /etc/inetd.conf

. This entry may have been

removed or commented out to prevent non-secure access.

Kerberos speciﬁc errors are listed in sis(5).

WARNINGS

The integrity of each host and the connecting medium is assumed if the "privileged port" authentication

procedure is used in a non-secure environment or if the command line options

-R or -r are used in a

secure environment. Although both these methods provide insecure access, they are useful in an "open"

environment. This is insecure, but is useful in an ‘‘open’’ environment.

Note that all the information, including any passwords, are passed unencrypted between the two hosts

when

rlogind is invoked in a non-secure environment.

AUTHOR

rlogind was developed by the University of California, Berkeley.

FILES

/etc/hosts.equiv List of equivalent hosts

$HOME/.rhosts User’s private equivalence list