HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
r
remshd(1M) Kerberos remshd(1M)
• in a secure environment, the command line options decide whether connection is to be
terminated.
-K if Kerberos authorization does not succeed the connection is terminated (see
sis(5) for details on authorization).
-R if the client’s host is not equivalent to the account accessed, the connection is ter-
minated.
-r if the account is not equivalent to the account accessed, then Kerberos authoriza-
tion has to succeed or the connection is terminated.
-k if Kerberos authorization fails, then the account has to be equivalent or the con-
nection is terminated. For more information on equivalent accounts, see
hosts.equiv(4).
10. A null byte is returned on the primary connection and the command line is passed to the normal
login shell of the user with that shell’s -c option. The shell inherits the network connections
established by remshd and assumes the normal user and group permissions of the user.
remshd uses the following path when executing the specified command:
/usr/bin:/usr/ccs/bin:/usr/bin/X11:/usr/contrib/bin:/usr/local/bin
11. If a secondary socket has been set up, remshd normally exits when command standard error
and secondary socket standard error have both been closed. If no secondary socket was set up,
remshd has called an exec(2) function, launched the command process, and is no longer present.
DIAGNOSTICS
All diagnostic messages are returned on the connection associated with standard error after which any net-
work connections are closed. An error is indicated by a leading byte with a value of 1 (0 is returned in step
9 above upon successful completion of all the steps before the command execution).
Malformed from address
The first socket connection does not use a reserved port or the client’s host address is not an Internet
address.
Can’t get stderr port
Unable to complete the connection of the secondary socket used for error communication.
Second port not reserved
The secondary socket connection does not use a reserved port.
Locuser too long
The name of the user account on the client’s host is longer than 16 characters.
Remuser too long
The name of the user on the server’s host is longer than 16 characters.
Command too long
The command line passed exceeds the size of the argument list (as configured into the system).
Login incorrect
No password file entry existed for the user name on the server’s host, or the authentication procedure
described above in step 8 failed.
No remote directory
The chdir command to the home directory or "/" on the server’s host failed.
Can’t make pipe
The pipe needed for the standard error output wasn’t created.
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.
Section 1M−−700 − 3 − HP-UX Release 11i: December 2000
___
___