hosting_queues_cron_cmd makes unwarranted assumptions about bash availablility

hosting_queues_cron_cmd() assumes that BASH is installed and available at /bin/bash. This is also true on most mainstream Linux distributions, but not all, and certainly not true on BSD-based systems (where, if installed, BASH is available at /usr/local/bin/bash).

So, is there any reason that we need BASH for this? Wouldn't /bin/sh do the job just as well (/bin/sh is guaranteed to be available on all Unix-based systems)?

Why do we even set the SHELL variable in the crontab? It's commonly set at the top of /etc/crontab system wide, and does not need to be set in each user’s crontab.

The code in question:

function hosting_queues_cron_cmd() {
  $command = _hosting_dispatch_cmd();
  $return = <<<END
SHELL=/bin/bash
PATH=$_SERVER[PATH]
*/1 * * * * $command
END;
  return $ret