Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 152021 - cron don't like CVS directory in /var/spool/cron or /etc/cron.d
cron don't like CVS directory in /var/spool/cron or /etc/cron.d
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: vixie-cron (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jason Vas Dias
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-03-24 09:19 EST by Peter Bieringer
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-24 10:29:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Bieringer 2005-03-24 09:19:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.6) Gecko/20050321 Firefox/1.0.2

Description of problem:
We're using a system CVS to track configuration changes properly.

cron isn't smart enough during running through its spool
directories and shows a strange message in logging (which also logwatch doesn't know)

Version-Release number of selected component (if applicable):
vixie-cron-4.1-20_EL and below

How reproducible:

Steps to Reproduce:
1. create CVS directory in /var/spool/cron and/or /etc/cron.d
2. take a look into /var/log/cron and/or daily logwatch result


Actual Results:  /var/log/cron:
Mar 24 15:06:01 host crond[6117]: (*system*) NOT REGULAR (/etc/cron.d/CVS)
Mar 24 15:06:01 host crond[6117]: (CVS) ORPHAN (no passwd entry)

logwatch result:
**Unmatched Entries**
NOT REGULAR (/etc/cron.d/CVS)

Expected Results:  cron is skipping at least a CVS directory.

Additional info:

Same issue already went up with
up2date: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114322
MAKEDEV: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150766
Comment 1 Jason Vas Dias 2005-03-24 10:29:39 EST
cron expects every entry in its /etc/cron.d directory to be a 
crontab file, and correctly warns you if it detects that an entry 
in that directory is not a regular file or a crontab .
Solution: do not create directories in the /etc/cron.d directory.

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