anchor.diff:  There are two ways that god can monitor your process. The first and better way
   is with process events. Not every system supports it, but those that do will
   automatically use it. With events, god will know immediately when a process
  -exits. For those systems without events support, god will use a polling
  -mechanism. The output you will see in this section will show both ways.
  +exits. For those systems without process event support, god will use a polling
  +mechanism. The output you see throughout this section will show both ways.
   
   After starting god, you should see some output like the following:
   
  
positive.code: end
  ```
  
  This is the simplest possible god configuration. In this example the
  `simple` process runs foreground, so god will take care of daemonizing it
  and keeping track of the PID for us. If the process is not running when god
  starts, it will be started. If the process dies, it will be restarted.
  
  To run god, we give it the config file we wrote with `-c`. To see what's going
  on, we can ask it to run foreground with `-D`:
  
  ```terminal
  $ god -c path/to/simple.god -D
  
negative.code: 
  Here I've specified a `:memory_max` option to the `keepalive` command. Now if
  the process memory usage goes above 150 megabytes, god will restart it.
  Similarly, by setting the `:cpu_max`, god will restart my process if its CPU
  usage goes over 50%. By default these properties will be checked every 30
  seconds and will be acted upon if there is an overage for three out of any
  five checks. This prevents the process from getting restarted for temporary
  