TABLE OF CONTENTS
- 1. programs/libram-record
- 1.1. libram-record/libram-record
- 1.2. libram-record/libramrecord
- 1.3. libram-record/libramrecord_close
- 1.4. libram-record/libramrecord_data
- 1.5. libram-record/libramrecord_exit
- 1.6. libram-record/libramrecord_fd
- 1.7. libram-record/libramrecord_free
- 1.8. libram-record/libramrecord_init
- 1.9. libram-record/libramrecord_open
- 1.10. libram-record/libramrecord_process
- 1.11. libram-record/libramrecord_result
- 1.12. libram-record/libramrecord_wait
- 1.13. libram-record/ramrecord_bh
- 2. programs/ramc-replay
programs/libram-record [ Generics ]
NAME
libram-record - file format used by ramc-replay and libram-record
DESCRIPTION
ramc-replay(1) replays data from file. The files can either be created by the user, or by recording sessions with libram-record(3).
The file format used by these utilities consists of blocks that consists of the libram method heder, the payload header, and the data.
The libram method header consists of the libram methods, the session id, the timestamp and further and parameters. The timestamp consists of the UNIX timestamp, optionally follow by up to six decimals after the decimal point (e.g. 1361357865, 1361357865.2 or 13613557865.200000). The possible methods and the parameters for each method is described below.
The payload header consists of the direction and the length of the payload of each method. The direction is eihter a < for data flowing from the client to the server or a > for data flowing from the server to the client. Immediate after the direction indicator is the length of the data, expressed a a decimal number. The payload line is terminated with a line feed.
After the method and the payload follows the (binary) payload. The length of this data is specified in the payload line. The payload is terminated with a line feed, so that the next block starts with a new line.
The blocks may be seperated either by empty lines, or by lines beginning with a # character. The remainer of the lines beginning with a # can be used as a comment to further describe the data.
The possible methods are:
- open: the parameters of the open header are the session id, the timestamp, the source ip address and port, the destination ip address and port, the ip protocol (either tcp or udp), and the connect string with further information to the backend. The paramters are seperated with spaces.
- data: the paramter of the data method, the session id and the timestamp
- close: the paramter to the close method, the session id and the timestamp
SEE ALSO
libram(3), libram-record(3), libram-record(5), libram-synchronous(3), libram-asynchronous(3), libram_init(3), libram_data(3), libram_close(3)
programs/ramc-replay [ Generics ]
NAME
ramc-replay - replay libram session
SYNOPSIS
ramc-replay [-V] [-h] [-v] [-s] [-b] [-r] [-t timeout] [-m modulepath] [-c connect] [-f replay] backend
DESCRIPTION
ramc-replay is a libram client (hence the prefix ramc) that replays data from file. The files can either be gernerated be the user itself, or recorded with the libram-record backend module.
Details about the replay data format can be found in libram-record(5).
The replay data file is specified using the -f option. If no -f option is given, ramc-replay reads the playback data from stdin.
ARGUMENTS
- -V: print version info. Specifying more than one -V outputs more information.
- -h: print usage information
- -v: be verbose about the data processing
- -s: try to use libram synchronous mode. See libram-synchronous(3) and libram-asynchronous(3) for details about the synchronous modes of libram(3)
- -b: try to use libram in nonblocking mode
- -r: try to reconnect to the libramrpc-server
- -t: set the timeout that ramc-replay in asynchronous mode is waiting for outstanding requests if the end of the record file is reached. The default value is 2s.
- -m: specify the the path where modules are searched. If this option is omitted, the environment variable LIBRAM_MODULEPATH is used. If this is empty, the module path used at configure time is used.
- -c: the connect string for the module. The connect strings are documented in the manual page of the corresponding module.
- -f: specifies the file from which to read the playback data. See libram-record(5) for details about the file format.
- module: specifies which module should be used by ramc-replay.
ENVIRONMENT
- LIBRAM_MODULEDIR: directory of libram modules
SEE ALSO
libram(3), libram-record(3), libram-record(5), libram-synchronous(3), libram-asynchronous(3)