Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 4766

Summary: New vixie-cron security package uses a 6.0 only logrotate feature
Product: [Retired] Red Hat Linux Reporter: Chris Siebenmann <cks-rhbugzilla>
Component: vixie-cronAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.2   
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: 2001-04-10 22:05:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Chris Siebenmann 1999-08-28 21:55:04 UTC
The new version of vixie-cron released for RedHat 5.2 to
fix a security problem (vixie-cron-3.0.1-36.5.2) uses a
feature of logrotate (the 'missingok' keyword) that is not
available in the version of the logrotate package released
for RedHat 5.2; 'missingok' is only supported in the
logrotate on 6.0+.

 The result is an email a night from every system with
the vixie cron update applied. In some environments, this
is a lot of mail. (It may also result in the cron log not
being rolled; I expect to find out soon.)

Comment 1 Chris Siebenmann 1999-08-28 22:00:59 UTC
On checking, I've discovered that this is already a known and fixed
bug in the cron package. My apologies for not checking thoroughly
enough *before* I filed this report; it can be discarded as fixed
already (or a duplicate).