Rcpd exists to copy files between machines. It listens for service
requests at the port indicated by the
services specification; see
Rcpd offers up files from the
directory (or another build-time configured directory), optionally
prepending the source IP address (followed by a /) to the filename
specified (again, optionally configured at build-time. The default
is not to do this).
Rcpd tries to offer the same security model as
tftpd by only writing to files that exist and are writable by user
and only reading from files that are readably by user
is specified, hostnames are reverse-resolved and connections are aborted
if addresses and names are not consistent.
Transport-level keepalive messages are enabled unless the
-n option is present. This is probably entirely irrelevent for