Bug 951725 - Bad month in unbound cron job
Summary: Bad month in unbound cron job
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: unbound
Version: rawhide
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-12 21:43 UTC by Jerry James
Modified: 2013-04-16 14:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-16 14:25:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jerry James 2013-04-12 21:43:35 UTC
Description of problem:
I see this in /var/log/cron on Rawhide:

Apr 12 15:12:02 rawhide32 crond[1041]: (CRON) bad month (/etc/cron.d/unbound-anchor)

The contents of that file are:

10 3 1 unbound /usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem

which is missing two fields.  There should be 5 fields at the start of the line: minute, hour, day of month, month, and day of week.  So cron thinks that "unbound" is month, which leads to the complaint.  The "unbound" word shouldn't be there at all, I think.  After the 5 time fields, everything else is executed as a command, IIUC.

Version-Release number of selected component (if applicable):
unbound-libs-1.4.20-4.fc20.i686

How reproducible:
Don't know.  Just saw this for the first time.

Steps to Reproduce:
1. Install unbound-libs
2. Wait for crond to run
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Paul Wouters 2013-04-12 23:40:47 UTC
Duh, after a day of scratch builds, still left with a silly error. Fixed in 1.4.20-5, thanks!

The "unbound" should be there, it is the uid to run the cron job as. But we were missing the two *'s


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