+++ This bug was initially created as a clone of Bug #142953 +++ Description of problem: In previous releases of FC it was possible to have r/o crontab files, for example an rpm which needs cron entries might drop a file into /etc/cron.d/my-package which was mode 444 or similar. This no longer works - the check in database.c around line 260 has the following code:- if ((statbuf->st_mode & 07733) != 0600) { log_it(fname, getpid(), "BAD FILE MODE", tabname); goto next_crontab; } which *enforces* the owner write bit. Although it may not be good practice to make these r/o (I would be prepared to argue this point), enforcing writability seems counter-intuitive, especially when you end up reading the damn source code to find out just what is wrong :-) Version-Release number of selected component (if applicable): vixie-cron-4.1-19 How reproducible: Every time Steps to Reproduce: 1. install -m444 mycrontab /etc/cron.d/mycrontab 2. look at output in /var/log/cron Additional info:
Fixed for bug Bug #142953 with vixie-cron-4.1-36.EL4.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-361.html