From: gga <GGarramuno@...>
Date: 2007-02-03T16:45:07+09:00
Subject: Re: proper usr/bin/env ruby shebang

On Feb 3, 12:25 am, Daniel DeLorme <dan...@dan42.com> wrote:
> Nobuyoshi Nakada wrote:
> > Do not rely on /usr/bin/env, it may not exist.
>
> Also, /usr/bin/env relies on the $PATH env variable,
> so if you try to run this as a cron job it will fail
> because $PATH is not set.
>
> Daniel

Again, that's probably bad sysadmin or user error in setting up cron.

> grep PATH /etc/crontab
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

If you run your own cron jobs as a normal user, you should create your
own similar crontab file.  You can do so with:

> crontab /etc/crontab
> crontab -e  # to edit it

(Depending on your linux flavor, your user cron file will be stored
in /var/spool/cron/crontabs/<user> (Unix/Slackware/*BSD),
/var/spool/cron/<user> (RedHat) or /var/cron/tabs/<user> (SuSE).