anchor.diff:  $ ./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`:
  
positive.code: This is much more scalable than being limited to the amount of memory space that you have.
  You can buy a redundant pair of 6TB of enterprise disks very much more cheaply than 6TB of memory.
  
  * *15. File handles and flushing data to the disk*
  
  As mentioned previously Chronicle Queue stores its data off-heap in a ‘.cq4’ file.
  
negative.code: `DocumentContext` available for reading:
  
  [source,java]
  ----
  // this will be true if there is at least one message in the queue
  boolean messageAvailable = tailer.toEnd().direction(TailerDirection.BACKWARD).
          readingDocument().isPresent();
  ----
  
  '''
  * *6. Restartable tailers*
  
  It can be useful to have a tailer which continues from where it was up to on restart of the application.
  