bpcounter(1) [debian man page]

BPCOUNTER(1)							  BP executables						      BPCOUNTER(1)

NAME

       bpcounter - Bundle Protocol reception test program

SYNOPSIS

       bpcounter ownEndpointId [maxCount]

DESCRIPTION

       bpcounter uses Bundle Protocol to receive application data units from a remote bpdriver application task.  When the total number of
       application data units it has received exceeds maxCount, it terminates and prints its reception count.  If maxCount is omitted, the default
       limit is 2 billion application data units.

EXIT STATUS

       0   bpcounter has terminated.  Any problems encountered during operation will be noted in the ion.log log file.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       Diagnostic messages produced by bpcounter 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.

       bpcounter bundle reception failed.
	   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), bpecho(1), bp(3)

perl v5.14.2							    2012-05-25							      BPCOUNTER(1)

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)