Bug 14081 - logrotate update should not change /etc/logrotate.conf
logrotate update should not change /etc/logrotate.conf
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: logrotate (Show other bugs)
6.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-16 16:08 EDT by Need Real Name
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: 2000-07-16 16:08:45 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 Need Real Name 2000-07-16 16:08:44 EDT
every time i upgrade logrotate i have to go an manually
mv /etc/logrotate.conf.rpmsave /etc/logrotate.conf

the package should not assume i want my configuration
changed.

thanks
-dean
Comment 1 Erik Troan 2000-07-31 12:53:29 EDT
Is it generating an .rpmsave file that you're having to restore? How many times
has this
happened? Occasionally (well, twice) we've had to change the logrotate file in a
way
that made this happen (upgrading to 6.2 and 6.0 would have given this behavior),
so if that's
when you saw it, it's a feature, not a bug :-( Specifically, we removed lastlog
from rotation and 
fixed the permission of wtmp on rotation.

If you've seen this behavior more prevalently then this, please reopen the bug.

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