Bad Minute Error in Crontab File

[David Hart]

On Wed, 2005-11-16 at 15:12 +0000, Hakim Singhji wrote:
>  <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.

It would be helpful if, as a previous poster in this thread asked, you
would post the contents of the file you are inputting to crontab (and
the exact error message produced).  How else are we supposed to know
what's happening? ;)

-- 
David Hart <ubuntu at tonix.org>