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

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

201

202

203

204

205

206

207

208

209

210

remshd(1M) remshd(1M)

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 conﬁgured into the system).

No password ﬁle entry existed for the user name on the server’s host, or the authentication pro-

cedure 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.

system call

: message

Error in executing the named system call. The message speciﬁes the cause of the failure.

shellname

: ...

The user’s login shell could not be started. This message is returned on the connection associated

with the standard error, and is not preceded by a leading byte with a value of 1. Other messages

can be returned by the remote command when it executes.

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 shell 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.

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

when

remshd is invoked in a non-secure environment.

remshd ignores SIGHUP, SIGINT, SIGQUIT, and SIGTERM, so these signal numbers can safely be sent

to remote commands via the secondary socket provided by remshd. Other signal numbers may cause

remshd to kill itself.

AUTHOR

remshd was developed by the University of California, Berkeley.

FILES

$HOME/.rhosts User’s private equivalence list

/etc/hosts.equiv List of equivalent hosts