anchor.diff:  
   You can dump the queue to the terminal using `net.openhft.chronicle.queue.main.DumpMain` or `net.openhft.chronicle.queue.ChronicleReaderMain`. `DumpMain` performs a simple dump to the terminal while `ChronicleReaderMain` handles more complex operations, e.g. tailing a queue. They can both be run from the command line in a number of ways described below.
   
  +'''
   * *8. DumpMain*
   
   If you have a project pom file that includes the Chronicle-Queue artifact, you can read a `cq4` file with the following command:
  
positive.code: $ ./bin/dump_queue.sh <file path>
  ----
  
  * *9. Reading a queue using `ChronicleReaderMain`*
  The second tool for logging the contents of the chronicle queue is the `ChronicleReaderMain` (in the Chronicle Queue project). As mentioned above, it is able to perform several operations beyond printing the file content to the console. For example, it can be used to tail a queue to detect whenever new messages are added (rather like $tail -f).
  
  Below is the command line interface used to configure `ChronicleReaderMain`:
  
negative.code: ==== A Quick start
  This section provides a quick reference for using Chronicle Queue to briefly show how to create, write/read into/from a queue.
  
  - Chronicle Queue construction
  
  Creating an instance of Chronicle Queue is different from just calling a constructor.
  To create an instance you have to use the `ChronicleQueueBuilder`.
  