anchor.diff:  1. Sends all output of the errand to the BOSH CLI for output
   1. Releases the deployment lock
   1. Releases the VM back into the resource pool
  - 
  +
   Use `bosh run errand ERRAND-NAME` to run an errand. ERRAND-NAME must be the name of an errand provided in the deployment manifest.
   
   Example:
  
positive.code: 
  #### <a id="job-monitoring"></a>Job Monitoring ####
  
  BOSH uses [monit](http://mmonit.com/monit/) to manage and monitor the health of 
  processes in an instance of a job.
  Using `monit`, BOSH can start, stop, and restart instances of a job when
  necessary.
  
negative.code: the `/var/vcap/sys/log/<errand-name>` directory.
  For example, BOSH writes the stdout log for an errand named "smoke-test" to
   `/var/vcap/sys/log/smoke-test/smoke-test.stdout.log`.
  
  <p class="note"><strong>Note</strong>: Since BOSH releases the VM back into the resource pool when an  errand completes, you cannot access any log files or screen output after this process finishes.</p>
  
  By default, BOSH streams errand output smaller than 1MB, stdout, and stderr to
  the screen.
  You must redirect errand output greater than 1MB to a file.
  
  To save output from a BOSH errand VM:
  
  1. In the BOSH errand script, redirect the output to a log file.
  1. Using the BOSH CLI, run `bosh errand` with the `--download-logs` option to
  download the log files.
  
  By default, BOSH downloads the logs to your present working directory.
  