Red Hat Bugzilla – Bug 85654
remove /etc/logrotate.d/apache it is dangerous
Last modified: 2007-04-18 12:51:51 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 Description of problem: /etc/logrotate.d/apache should (IMO) be dropped. restarting apache is something I want to be in control of To rotate my logs I use CustomLog "|/usr/sbin/rotatelogs <logfile> 86400" vhost If I change my httpd.conf I want to apply it when I'm ready NOT BEFORE why do you want to use logrotate? whats wrong with rotatelogs ( and not restarting apache all the time) do I have to set a cron job to delete /etc/logrotate.d/apache ? can I tell rpm/up2date to ignire this file? can I set my system to run a script everytime rpm/up2date runs (so I can put 'rm /etc/logrotate.d/apache' in it) 3 times in the past year I've had a server outage thanks to /etc/logrotate.d/apache. I might as well put it in my login script! Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. use rpr or up2date 2. use apache 3. use logrotate Actual Results: buggers up apache Expected Results: leave apache alone Additional info:
We should mark logrotate.d/apache as %config(noreplace), so that you make it an empty file (or comment out the conents), and it won't be overwritten on upgrades. Thanks for the report.
/etc/logrotate.d/httpd is now marked config(noreplace) in httpd-2.0.45-4, so you can make this an empty file and prevent your logs getting rotated.
This is fixed in current releases of Red Hat Enterprise Linux and Fedora Core.