bpecho(1) [debian man page]
BPECHO(1) BP executables BPECHO(1) NAME
bpecho - Bundle Protocol reception test program SYNOPSIS
bpecho ownEndpointId DESCRIPTION
bpecho uses Bundle Protocol to receive application data units from a remote bpdriver application task. In response to each received application data unit it sends back an "echo" application data unit of length 2, the NULL-terminated string "x". bpecho terminates upon receiving the SIGQUIT signal, i.e., ^C from the keyboard. EXIT STATUS
0 bpecho has terminated normally. Any problems encountered during operation will be noted in the ion.log log file. 1 bpecho has terminated due to a BP reception failure. Details should be noted in the ion.log log file. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
Diagnostic messages produced by bpecho are written to the ION log file ion.log. Can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. Can't open own endpoint. Another application has already opened ownEndpointId. Terminate that application and rerun. bpecho bundle reception failed. BP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. No space for ZCO extent. ION system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. Can't create ZCO. ION system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. bpecho can't send echo 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
bpadmin(1), bpdriver(1), bpcounter(1), bp(3) perl v5.14.2 2012-05-25 BPECHO(1)
Check Out this Related Man Page
BPRECVFILE(1) BP executables BPRECVFILE(1) NAME
bprecvfile - Bundle Protocol (BP) file reception utility SYNOPSIS
bprecvfile own_endpoint_ID DESCRIPTION
bprecvfile is intended to serve as the counterpart to bpsendfile. It uses bp_receive() to receive bundles containing file content. The content of each bundle is simply written to a file named "testfileN" where N is the total number of bundles received since the program began running. Use ^C to terminate the program. EXIT STATUS
0 bprecvfile 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. bprecvfile bundle reception failed. BP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. bprecvfile: can't open test file File system error. bprecvfile terminates. bprecvfile: can't receive bundle content. BP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. bprecvfile: can't write to test file File system error. bprecvfile terminates. bprecvfile cannot continue. BP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. bprecvfile: can't handle bundle delivery. 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
bpsendfile(1), bp(3) perl v5.14.2 2012-05-25 BPRECVFILE(1)