Bug 671380 - Example omission within /etc/crontab
Summary: Example omission within /etc/crontab
Keywords:
Status: CLOSED DUPLICATE of bug 609544
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: crontabs
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marcela Mašláňová
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-21 13:21 UTC by daryl herzmann
Modified: 2011-02-18 09:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-18 09:04:34 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description daryl herzmann 2011-01-21 13:21:44 UTC
It was cool to find a fancy ASCII example within the installed /etc/crontab like so:

# Example of job definition:
# .---------------- minute (0 - 59)
# |  .------------- hour (0 - 23)
# |  |  .---------- day of month (1 - 31)
# |  |  |  .------- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  *  command to be executed


The only problem is that this is missing a key component, the username to run the command as.  Without the username, cron logs:

Jan 21 07:15:01 xxx crond[2290]: (*system*) RELOAD (/etc/crontab)
Jan 21 07:15:01 xxx crond[2290]: (CRON) bad username (/etc/crontab)
Jan 21 07:15:01 xxx crond[2290]: (CRON) bad command (/etc/crontab)
Jan 21 07:15:01 xxx crond[2290]: (CRON) bad command (/etc/crontab)

thank you

Comment 2 RHEL Program Management 2011-01-21 13:48:14 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Marcela Mašláňová 2011-02-18 09:04:34 UTC

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


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