|mlog - Message log file of Transactor
|This manual page describes the message log file of transactor, an general purpose transaction coordinator.
|Transactor's message log is a rotating log of currently relevant messages. It is purged (i.e. obsolete message are removed) on startup, and then at times when it seems opportune.
|It may grow to very large sizes if large transactions are handled by the system. The message log may hold the size equivalent of a few hundred transactions.
|The directory holding it must allow for creation of new files, renaming and deleting of files, as the message log must be atomically replaced.
|Each message starts by a keyword in the first column of a new line. The keyword is followed by the message index, the peer to or from which the message was transmitted, and a few qualifications indicating to what phase of the consensus protocol the message belongs.
|The message may include payload data, which is run-length encoded, starting by the length in bytes, and then by the binary data itself. In the binary data, each newline character is replaced by a combination of newline and tab, so that continuation lines can be clearly identified by a human viewer.
|The location of the message log must be specified as an absolute path in the configuration file.
|transactor(8), transactor.conf(5), transactor_tlog(5)
|Transactor is Copyright 2003, 2004 Claus Fischer
|Transactor was written by Claus Fischer <email@example.com>.