🚀 go-pugleaf

Thanks a lot, it works great now with the command:

0 0 * * * /usr/bin/local/elm -s "Daily Comics" carheden <
/m/j/carheden/comics.txt

(Sorry, I like 0's, unless you have a good reason why they're bad :)

Unfortunatly, I also get a message from the daemon (this refers to the
cron program, right):

Sending mail...
Mail sent!

*************************************************
Cron: The previous message is the standard output
      and standard error of one of your cron commands.

A little help on redirecting stdout.  Can I just append 2>/dev/null? 
This will just send elm's screen output there, right, not my message.

TIA

Mike Loseke wrote:
>  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.

-- 
Adam
carheden@holly.colostate.edu
http://holly.ColoState.edu/~carheden