Red Hat Bugzilla – Bug 170808
crontab hangs on invalid input
Last modified: 2007-11-30 17:07:08 EST
+++ This bug was initially created as a clone of Bug #89937 +++
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
Version-Release number of selected component (if applicable):
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 comment from email@example.com on 2004-04-05 16:30 EST --
Reassigning to queue owner. Not sure how it got assigned to me...
-- Additional comment from firstname.lastname@example.org on 2004-06-30 12:40 EST --
*** Bug 114386 has been marked as a duplicate of this bug. ***
-- Additional comment from email@example.com on 2004-06-30 12:41 EST --
Should get fixed in 3.0.1-94.
-- Additional comment from firstname.lastname@example.org on 2004-08-30 19:06 EST --
This was fixed in 3.0.1-94 & in current version : vixie-cron-4.1-10.
-- Additional comment from email@example.com on 2005-07-12 21:53 EST --
I recommend cloning a bug for this for RHEL3.
-- Additional comment from firstname.lastname@example.org on 2005-07-20 17:58 EST --
Withholding PM ACK; vixie-cron does not currently have a QA slot allocated to it
This bug is fixed with vixie-cron-4.1-8_EL3, available from:
and should be considered for inclusion in RHEL-3-U7 .
Fixed with vixie-cron-4.1-10.EL3, currently in RHEL-3-U7 with errata