blob: 73d1ef47a678ae807e51b6dc993756cbb6659e5d [file] [log] [blame]
E. Scott Danielse8a5b2c2019-04-22 17:04:10 +00001
2This directory contains various sender/receiver applications that can be
3driven together to test message exchange through the RMr library.
4The run_app_test.ksh script should support building the library, building
5a sender and receiver, then running a short test to verify.
6
7The basic sender and receiver
8Sender and receiver perform lightweight check sums on the message body
9and on trace data to verify that the messages are being reeived correctly.
10The receiver acks message type 5, so the reciver should receive acks at
11about the volume of 1/10th the number of messages sent.
12
E. Scott Daniels71df2a22021-03-10 12:22:44 -050013
14The contents of this directory are generally intended to support automated
15testing via the run_all.sh script. Howerver, there may be times where
16building and running the tools manually is needed. To support this two
17scripts, maker.sh and runner.sh, are provided. The maker.sh script will
18build RMR in ../../.build and install it in a /tmp directory so that the
19needed include files can be found when building the test programmes. The
20runner.sh script sets the environment and then starts the comand given.
21For example, to run the sencder:
22 RMR_SEED_RT=xx.rt runner.sh ./sender 1000 0 0
23
24The runner script accepts both -v and -d to set verbose and debug options
25for RMR when the programme is run.
26
27
28The maker script will always build the test programmes whether they've been
29changed or not. By default the current .deb packages in ../../.build are
30used, but the -b option can be given to force a rebuild of the RMR libraries
31in addition to building the tools. If the ../../.build directory does not
32exist, it should automatically be created and RMR built.
33