file2dgr(1) [debian man page]
FILE2DGR(1) DGR executables FILE2DGR(1) NAME
file2dgr - DGR transmission test program SYNOPSIS
file2dgr remoteHostName fileName [nbrOfCycles] DESCRIPTION
file2dgr uses DGR to send nbrOfCycles copies of the text of the file named fileName to the dgr2file process running on the computer identified by remoteHostName. If not specified (or if less than 1), nbrOfCycles defaults to 1. After sending all lines of the file, file2dgr sends a datagram containing an EOF string (the ASCII text "*** End of the file ***") before reopening the file and starting transmission of the next copy. When all copies of the file have been sent, file2dgr prints a performance report: Bytes sent = I<byteCount>, usec elapsed = I<elapsedTime>. Sending I<dataRate> bits per second. EXIT STATUS
0 file2dgr has terminated. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
Diagnostic messages produced by file2dgr are written to the ION log file ion.log. Can't open dgr service. ION system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. Can't open input file Operating system error. Check errtext, correct problem, and rerun. Can't acquire DGR working memory. ION system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. Can't reopen input file Operating system error. Check errtext, correct problem, and rerun. Can't read from input file Operating system error. Check errtext, correct problem, and rerun. dgr_send failed. ION 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
file2dgr(1), dgr(3) perl v5.14.2 2012-05-25 FILE2DGR(1)
Check Out this Related 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)