Bad Minute Error in Crontab File

[Hakim Singhji]

 <sean <at> seanmiller.net> writes:
> I would not recommend calling a crontab file something like ~/bin/sig -
> it's very unintuitive, assuming that is what you meant to do and this is
> not a mistake.

I'm afraid that I may misunderstand how crontab works. See I was trying to run 
the file ~/bin/sig using crontab. I thought that crontab schedule the time 
sequence for jobs to repeat and the last argument on the line was the filename 
to be executed. Is this not correct? If someone could show me there an example 
of "crontab -e". This may be helpful.

> Personally I would also archive them so that if you muck up the crontab
> you can look back at what it was before.

Good idea... what program could do this tar? Or should I write a shell script 
that adds random #'s.

Hakim