Bug 188501 - Cronjobs from /etc/cron.d does not run
Summary: Cronjobs from /etc/cron.d does not run
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: vixie-cron
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-10 17:47 UTC by Lars Berntzon
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-12 20:22:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.
'


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