HP-UX Reference (11i v1 05/09) - 1 User Commands N-Z (vol 2)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

251

252

253

254

255

256

257

258

259

260

rcp(1) Kerberos rcp(1)

remsh rhost1 -l ruser1 rcp path1 ruser2@rhost2:path2

Therefore, for a such a transfer to succeed, ruser2 on rhost2 must allow access by ruser1 from rhost1 (see

hosts.equiv(4)).

WARNINGS

The

rcp routine is confused by any output generated by commands in a

.cshrc ﬁle on the remote host

(see csh(1)).

Copying a ﬁle onto itself, for example:

rcp path ‘hostname‘:path

may produce inconsistent results. The current HP-UX version of

rcp simply copies the ﬁle over itself.

However, some implementations of

rcp, including some earlier HP-UX implementations, corrupt the ﬁle.

In addition, the same ﬁle may be referred to in multiple ways, for example, via hard links, symbolic links,

or NFS. It is not guaranteed that

rcp will correctly copy a ﬁle over itself in all cases.

Implementations of

rcp based on the 4.2BSD version (including the implementations of

rcp prior to HP-

UX 7.0) require that remote users be speciﬁed as rhost.ruser. If the ﬁrst remote host speciﬁed in a third

party transfer (rhost1 in the example below) uses this older syntax, the command must have the form:

rcp ruser1@rhost1:path1 rhost2.ruser2:path2

since the target is interpreted by rhost1. A common problem that is encountered is when two remote ﬁles

are to be copied to a remote target that speciﬁes a remote user. If the two remote source systems, rhost1

and rhost2, each expect a different form for the remote target, the command:

rcp rhost1:path1 rhost2:path2 rhost3.ruser3:path3

will certainly fail on one of the source systems. Perform such a transfer using two separate commands.

DIAGNOSTICS

Diagnostics can occur from both the local and remote hosts. Those that occur on the local host before the

connection is completely established are written to standard error. Once the connection is established, any

error messages from the remote host are written to standard output, like any other data.

Error! could not retrieve authentication type.

Please notify sys admin.

There are two authentication mechanisms used by

rcp. One authentication mechanism is based on

Kerberos and the other is not. The type of authentication mechanism is obtained from a system ﬁle

which is updated by inetsvcs_sec(1M). If the system ﬁle does not contain known authentication types,

the above error is displayed.

AUTHOR

rcp was developed by the University of California, Berkeley.