SYNOPSIS
bprecvfile own_endpoint_ID [max_files]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.If a max_files value of N (where N > 0) is provided, the program will terminate automatically upon completing its Nth file reception. Otherwise it will run indefinitely; 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.