Bug 81449 - upgrade replaces deliberately removed files
upgrade replaces deliberately removed files
Product: Red Hat Linux
Classification: Retired
Component: logrotate (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Elliot Lee
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-01-09 11:42 EST by Neil Prockter
Modified: 2015-01-07 19:02 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-09 18:02:24 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 Neil Prockter 2003-01-09 11:42:23 EST
Description of problem: I don't want logrotate restarting apache EVER. I remove
/var/logrotate.d/apache but upgrading puts it back again. Can an upgrade be made
to not recreated files that have been removed? Alternatively can some sense be
added to logrotate? alternatively can we have a version of logrotate that never
restarts system daemons

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. remove /etc/logrotate.d/apache
2. upgrade
Actual results:
apache gets restarted every day

Expected results:
leave apache alone

Additional info:
if I've changed my apache config logrotate applies it! very bad!
Comment 1 Michael Lee Yohe 2003-01-09 12:12:31 EST
Resolution == NOTABUG

The way the packages are distributed by Red Hat, you will have the behavior you
don't like.  Therefore, if you upgrade a package, RPM will restore the
filesystem will the hierarchy that the packager (Red Hat) has determined.

For your other requests, you should simply open an RFE (request for enhancement)
bug to ask for logrotate to not restart daemons -- this is because your request
is a completely separate issue.
Comment 2 Neil Prockter 2003-01-09 18:02:24 EST
fair enough I've submitted a few enhancement request

Many Thanks

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