From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

Description of problem:
When entering an illegal crontab, crontab hangs and consumes 100% of cpu time.
Yes, you could say this is user error, but the error recovery of crontab should
be improved.

Version-Release number of selected component (if applicable):
vixie-cron-3.0.1-69

How reproducible:
Always

Steps to Reproduce:
1. Call crontab -e on the command line.
2. Add a line which reads:

*/__WONKY__ * * * * /bin/true

3. Save and exit the editor.

Actual Results:  The editor never exits, crontab consumes 100% of cpu time.

Expected Results:  An error should be returned. Something like:

crontab: installing new crontab
"/tmp/crontab.16807":1: bad minute
errors in crontab file, can't install.
Do you want to retry the same edit?


Additional info: