Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bpcp(1) [debian man page]

BPCP(1) 							 CFDP executables							   BPCP(1)

NAME
bpcp - A remote copy utility for delay tolerant networks utilizing NASA JPL's Interplanetary Overlay Network (ION) SYNOPSIS
bpcp [-dqr | -v] [-L bundle_lifetime] [-C custody_on/off] [-S class_of_service] [host1:]file1 ... [host2:]file2 DESCRIPTION
bpcp copies files between hosts utilizing NASA JPL's Interplanetary Overlay Network (ION) to provide a delay tolerant network. File copies from local to remote, remote to local, or remote to remote are permitted. bpcp depends on ION to do any authentication or encryption of file transfers. All covergence layers over which bpcp runs MUST be reliable. The options are permitted as follows: -d Debug output. Repeat for increased verbosity. -q Quiet. Do not output status messages. -r Recursive. -v Display version information. -L bundle_lifetime Bundle lifetime in seconds. Default is 86400 seconds (1 day). -C BP_custody Acceptable values are ON/OFF,YES/NO,1/0. Default is ON. -S class_of_service Bundle Protocol Class of Service for this transfer. Available options are: 0 Bulk Priority 1 Standard Priority 2 Expedited Priority Default is Standard Priority. bpcp utilizes CFDP to preform the actual file transfers. This has several important implications. First, ION's CFDP implementation requires that reliable convergence layers be used to transfer the data. Second, file permissions are not transferred. Files will be made executable on copy. Third, symbolic links are ignored for local to remote transfers and their target is copied for remote transfers. Fourth, all hosts must be specified using ION's IPN naming scheme. In order to preform remote to local transfers or remote to remote transfers, bpcpd must be running on the remote hosts. However, bpcp should NOT be run simultaneously with bpcpd or cfdptest. EXIT STATUS
0 bpcp terminated normally. 1 bpcp terminated abnormally. Check console and the ion.log file for error messages. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpcpd(1), ion(3), cfdptest(1) perl v5.14.2 2012-05-25 BPCP(1)

Check Out this Related Man Page

IPNADMIN(1)							  BP executables						       IPNADMIN(1)

NAME
ipnadmin - Interplanetary Internet (IPN) scheme administration interface SYNOPSIS
ipnadmin [ commands_filename ] DESCRIPTION
ipnadmin configures the local ION node's routing of bundles to endpoints whose IDs conform to the ipn endpoint ID scheme. ipn is a CBHE- conformant scheme; that is, every endpoint ID in the ipn scheme is a string of the form "ipn:element_number.service_number" where element_number is a CBHE "node number" and service_number identifies a specific application processing point. ipnadmin operates in response to IPN scheme configuration commands found in the file commands_filename, if provided; if not, ipnadmin prints a simple prompt (:) so that the user may type commands directly into standard input. The format of commands for commands_filename can be queried from ipnadmin with the 'h' or '?' commands at the prompt. The commands are documented in ipnrc(5). EXIT STATUS
0 Successful completion of IPN scheme administration. 1 Unsuccessful completion of IPN scheme administration, due to inability to attach to the Bundle Protocol system or to initialize the IPN scheme. EXAMPLES
ipnadmin Enter interactive IPN scheme configuration command entry mode. ipnadmin host1.ipnrc Execute all configuration commands in host1.ipnrc, then terminate immediately. FILES
See ipnrc(5) for details of the IPN scheme configuration commands. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
Note: all ION administration utilities expect source file input to be lines of ASCII text that are NL-delimited. If you edit the ipnrc file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to ipnadmin. Otherwise ipnadmin will detect syntax errors and will not function satisfactorily. The following diagnostics may be issued to the logfile ion.log: ipnadmin can't attach to BP. Bundle Protocol has not been initialized on this computer. You need to run bpadmin(1) first. ipnadmin can't initialize routing database. There is no SDR data store for ipnadmin to use. Please run ionadmin(1) to start the local ION node. Can't open command file... The commands_filename specified in the command line doesn't exist. Various errors that don't cause ipnadmin to fail but are noted in the ion.log log file may be caused by improperly formatted commands given at the prompt or in the commands_filename file. Please see ipnrc(5) for details. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
ipnrc(5) perl v5.14.2 2012-05-25 IPNADMIN(1)
Man Page