🚀 go-pugleaf

Thus spake <carheden@holly.colostate.edu>:
>My holly crontab gave me an error this morning.  Last night I added the
>line:
>
>0 0 * * * elm -s "Daily Comics" carheden <comics.txt
>
>to mail myself the URL's of my favortie comics contained in the file
>comics.txt in my home directory.  This line works just fine from the
>command line, but my crontab gave me the error:
>
>bsh: elm: not found
>
>*************************************************
>Cron: The previous message is the standard output
>      and standard error of one of your cron commands.
>
>Any ideas of how to fix this would be appreciated.  Thanks.

 You should give the full path to the executable and to the file as well.
You should be able to do a "which elm" at a shell prompt to find out
exactly where it is. It might be in /usr/bin/elm or /usr/local/bin/elm or
someplace like that.  You'll have to add the whole path in the crontab as
crond doesn't know about non-standard paths, or read your startup files,
to find binaries.

 For instance:

1 0 * * * /usr/local/bin/elm -s "Daily Comics" username < /path/to/file

(I don't like using all zero's in a crontab.)

-- 
   Mike Loseke    | Users are simply nature's way of
 mike@verinet.com | keeping me from hogging the processor.