title: What is the benefit of wrapping a PHP cron job inside a Bourne Shell Script (.sh)?
body: <p>I've come across a checklist for creating a new PHP cron at my job and one of the directions is:</p>
  
  <blockquote>
    <p>Add a wrapper file that calls the main part of your job code as
    cron_[name].sh</p>
  </blockquote>
  
  <p>A sample cron.sh:</p>
  
  <pre><code>#!/bin/sh
  ###########################################################
  # This job sends out the daily digest emails
  ###########################################################
  . $DS_JOBS_DIR/cron_common.sh
  
  cd $DS_JOBS_DIR/digests
  $DS_PHP daily_digest.php
  </code></pre>
  
  <p>What is the benefit of wrapping a PHP cron inside a shell script?</p>