bpsendfile(1) [debian man page]
BPSENDFILE(1) BP executables BPSENDFILE(1) NAME
bpsendfile - Bundle Protocol (BP) file transmission utility SYNOPSIS
bpsendfile own_endpoint_ID destination_endpoint_ID file_name [class_of_service] DESCRIPTION
bpsendfile uses bp_send() to issue a single bundle to a designated destination endpoint, containing the contents of the file identified by file_name, then terminates. The bundle is sent with no custody transfer requested, with TTL of 300 seconds (5 minutes). When class_of_service is omitted, the bundle is sent at standard priority; for details of the class_of_service parameter, see bptrace(1). EXIT STATUS
0 bpsendfile has terminated. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: Can't attach to BP. bpadmin has not yet initialized BP operations. Can't open own endpoint. Another BP application task currently has own_endpoint_ID open for bundle origination and reception. Try again after that task has terminated. If no such task exists, it may have crashed while still holding the endpoint open; the easiest workaround is to select a different source endpoint. Can't stat the file Operating system error. Check errtext, correct problem, and rerun. bpsendfile can't create file ref. Probably an unrecoverable database error, in which case the local ION node must be terminated and re-initialized. bpsendfile can't create ZCO. Probably an unrecoverable database error, in which case the local ION node must be terminated and re-initialized. bpsendfile can't send file in bundle. BP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bprecvfile(1), bp(3) perl v5.14.2 2012-05-25 BPSENDFILE(1)
Check Out this Related Man Page
IPNADMINEP(1) BP executables IPNADMINEP(1) NAME
ipnadminep - administrative endpoint task for the IPN scheme SYNOPSIS
ipnadminep DESCRIPTION
ipnadminep is a background "daemon" task that receives and processes administrative bundles (all custody signals and, nominally, all bundle status reports) that are sent to the IPN-scheme administrative endpoint on the local ION node, if and only if such an endpoint was established by bpadmin. It is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of Bundle Protocol on the local ION node, and it is terminated by bpadmin in response to an 'x' (STOP) command. ipnadminep can also be spawned and terminated in response to START and STOP commands that pertain specifically to the IPN scheme. ipnadminep responds to custody signals as specified in the Bundle Protocol specification, RFC 5050. It responds to bundle status reports by logging ASCII text messages describing the reported activity. EXIT STATUS
0 ipnadminep terminated, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem identified in the log file and use bpadmin to restart ipnadminep. 1 ipnadminep was unable to attach to Bundle Protocol operations or was unable to load the IPN scheme database, probably because bpadmin has not yet been run. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: ipnadminep can't attach to BP. bpadmin has not yet initialized BP operations. ipnadminep can't load routing database. ipnadmin has not yet initialized the IPN scheme. ipnadminep crashed. An unrecoverable database error was encountered. ipnadminep terminates. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), ipnadmin(1), bprc(5). perl v5.14.2 2012-05-25 IPNADMINEP(1)