Bug 4766 - New vixie-cron security package uses a 6.0 only logrotate feature
New vixie-cron security package uses a 6.0 only logrotate feature
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: vixie-cron (Show other bugs)
5.2
All Linux
low Severity low
: ---
: ---
Assigned To: Crutcher Dunnavant
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-28 17:55 EDT by Chris Siebenmann
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-10 18:05:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Siebenmann 1999-08-28 17:55:04 EDT
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 18:00:59 EDT
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).

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