|Summary:||upgrade replaces deliberately removed files|
|Product:||[Retired] Red Hat Linux||Reporter:||Neil Prockter <prockter>|
|Component:||logrotate||Assignee:||Elliot Lee <sopwith>|
|Status:||CLOSED NOTABUG||QA Contact:||Jay Turner <jturner>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2003-01-09 23:02:24 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Neil Prockter 2003-01-09 16:42:23 UTC
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 3. 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 17:12:31 UTC
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 23:02:24 UTC
fair enough I've submitted a few enhancement request Many Thanks