Bug 188501

Summary: Cronjobs from /etc/cron.d does not run
Product: [Fedora] Fedora Reporter: Lars Berntzon <lars.berntzon>
Component: vixie-cronAssignee: Jason Vas Dias <jvdias>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-12 20:22:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lars Berntzon 2006-04-10 17:47:43 UTC 
Description of problem:

Cron does not run jobs in the directory /etc/cron.d

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

This happens for both FC3 and FC4.

How reproducible:

Always

Steps to Reproduce:
1. Create a crontab style file in /etc/cron.d. Make it only writeable by owner
root and not executable.
2. Set the time for the job a couple of minutes in the future
3. Look at the /var/log/cron file. 
  
Actual results:

Cron does notice that the file is changed, my log looks like this:
Apr 10 19:32:01 xella35 crond[2369]: (*system*) RELOAD (/etc/cron.d/rsync-backup)

But then nothing more happens.


Expected results:

The job should be started.

Additional info:
Comment 1 Lars Berntzon 2006-04-10 18:12:08 UTC 
Aha, just found it. Files in the /etc/cron.d has to have an extra field for
which user to run as. So the format should be
<min> <hour> <day> <mon> <weekday> <user> <command> ...

So this is really a documentation bug.
Comment 2 Jason Vas Dias 2006-04-12 20:22:14 UTC 
From 'man 5 crontab:'
'
  Each line has five time and date fields, followed by a user  name  
  if this is a system crontab  file,  followed  by a command.
'