pdcp.1 (2012 03)

pdsh(1) pdsh-2.16 pdsh(1)
(hpux11.31)
NAME
pdcp - copy files to groups of hosts in parallel
rpdcp - (reverse pdcp) copy files from a group of hosts in parallel
SYNOPSIS
pdcp [options]... src [src2...] dest
rpdcp [options]... src [src2...] dir
DESCRIPTION
pdcp is a variant of the rcp(1) command. Unlike rcp(1), which copies files to a single remote host, pdcp
can copy files to multiple remote hosts in parallel. However, pdcp does not recognize files in the format
‘‘rname@rhost:path,’’ therefore all source files must be on the local host machine. Destination nodes must
be listed on the pdcp command line using a suitable target nodelist option (See the OPTIONS section
below). Each destination node listed must have pdcp installed for the copy to succeed.
When pdcp receives SIGINT (ctrl-C), it lists the status of current threads. A second SIGINT within one
second terminates the program. Pending threads may be canceled by issuing ctrl-Z within one second of
ctrl-C. Pending threads are those that have not yet been initiated, or are still in the process of connecting
to the remote host.
Like pdsh(1), the functionality of pdcp may be supplemented by dynamically loadable modules. In pdcp,
the modules may provide a new connect protocol (replacing the standard rsh(1) protocol), filtering options
(e.g. excluding hosts that are down), and/or host selection options (e.g. -a selects all nodes from a local
config file). By default, pdcp requires at least one "rcmd" module to be loaded (to provide the channel for
remote copy).
REVERSE PDCP
rpdcp performs a reverse parallel copy. Rather than copying files to remote hosts, files are retrieved
from remote hosts and stored locally. All directories or files retrieved will be stored with their remote
hostname appended to the filename. The destination file must be a directory when this option is used.
In other respects, rpdcp is exactly like pdcp, and further statements regarding pdcp in this manual also
apply to rpdcp.
RCMD MODULES
The method by which pdcp connects to remote hosts may be selected at runtime using the -R option (See
OPTIONS below). This functionality is ultimately implemented via dynamically loadable modules, and so
the list of available options may be different from installation to installation. A list of currently available
rcmd modules is printed when using any of the -h, -V,or-L options. The default rcmd module will also be
displayed with the -h and -V options.
A list of rcmd modules currently distributed with pdcp follows.
rsh Uses an internal, thread-safe implementation of BSD rcmd(3) to run commands using the stan-
dard rsh(1) protocol.
ssh Uses a variant of popen(3) to run multiple copies of the ssh(1) command.
mrsh This module uses the mrsh(1) protocol to execute jobs on remote hosts. The mrsh protocol uses a
credential based authentication, forgoing the need to allocate reserved ports. In other aspects, it
acts just like rsh.
krb4 The krb4 module allows users to execute remote commands after authenticating with kerberos.
Of course, the remote rshd daemons must be kerberized.
xcpu The xcpu module uses the xcpu service to execute remote commands.
OPTIONS
The list of available pdcp options is determined at runtime by supplementing the list of standard pdcp
options with any options provided by loaded rcmd and misc modules. In some cases, options provided by
modules may conflict with each other. In these cases, the modules are incompatible and the first module
loaded wins.
Standard target nodelist options
-w host,host,...
Target the specified list of hosts. Do not use with any other node selection options (e.g. -a, -g if they
are available). No spaces are allowed in the comma-separated list. A list consisting of a single ‘-’
HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1