Bug 163341 - crond failed to parse entry in a crontab
crond failed to parse entry in a crontab
Status: CLOSED DUPLICATE of bug 137962
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: vixie-cron (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-07-15 07:36 EDT by Hiroki Taira
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-15 09:54:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
crontab file (542 bytes, text/plain)
2005-07-15 07:36 EDT, Hiroki Taira
no flags Details

  None (edit)
Description Hiroki Taira 2005-07-15 07:36:00 EDT
Description of problem:

crond doesn't fork any commands
after entering entries that can't be parsed.

Version-Release number of selected component (if applicable):


How reproducible:

Creating crontab file in which there are entries
that can't be parsed.

Steps to Reproduce:

1. create the file named "/etc/cron.d/clean_tmp"
2. input the entry like following in the file.

0 */0,6,12,18 * * * root find /usr/local/hde/lc/backup/tmp/session -name ".[0-
9a-f]*" -a -cmin +360 -exec rm -rf "{}" \; >/dev/null 2>&1
Actual results:

Any commands in crontab are not executed ever.

Expected results:

same above.

Additional info:

After changing the entry following, crond has got started again.

0 0,6,12,18 * * * root find /usr/local/hde/lc/backup/tmp/session -name ".[0-9a-
f]*" -a -cmin +360 -exec rm -rf "{}" \; >/dev/null 2>&1
Comment 1 Hiroki Taira 2005-07-15 07:36:01 EDT
Created attachment 116793 [details]
crontab file
Comment 2 Jason Vas Dias 2005-07-15 09:54:58 EDT
I think cron was confused by the "0 */0..." entry, which is pretty meaningless:
"every hour, skipping 0 hours" - a synonym for "0 0..." .
What was your intention with the "0 */0" entry ?
Yes, cron needs improvement in reporting crontab parse errors - currently, it
simply ignores them, as have all previous versions of cron.
I am currently working on an enhanced version of cron that will report cron
syntax errors, a feature that has been requested before: bug 137962 .


*** This bug has been marked as a duplicate of 137962 ***

Note You need to log in before you can comment on or make changes to this bug.