anchor.diff:  ----
   $ less log.txt
   ----
  -
  -Each message contains identifier and name of the process and thread which produced
  -the message, then its verbosity level, and also source file, line and function
  -describing specific place of its origin.
   
   ==== Debug mode
   Debug mode is useful for programmers. You need to build OpenSCAP from source code
  
positive.code: There is no need to special compilation, the feature is available for all
  OpenSCAP users.
  
  To turn the verbose mode on, run ```oscap``` with both those two options:
  
  * ```--verbose VERBOSITY_LEVEL``` - Turn on verbose mode at specified
  verbosity level.
  * ```--verbose-log-file FILE``` - Provide name of a log file that the log
  will be written into.
  
  The ```VERBOSITY_LEVEL``` can be one of:
  
  
negative.code: 3. *WARNING* - possible failures which OpenSCAP can recover from
  4. *ERROR* - shows only serious errors
  
  The verbose messages will be written on standard error output (stderr).
  Optionally, you can write the log into a file using
   ```--verbose-log-file FILE```.
  
  This is an example describing how to run OpenSCAP in verbose mode:
  
  