bpecho1

Usage

Overview

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.