Bug 81497

Summary: don't restart daemons
Product: [Retired] Red Hat Linux Reporter: Neil Prockter <prockter>
Component: logrotateAssignee: Elliot Lee <sopwith>
Status: CLOSED NOTABUG QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-13 19:24:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neil Prockter 2003-01-09 22:29:29 UTC
Description of problem: logrotate restarts systems daemons, whilst this maybe
fine for desktops for servers this can be disasterous


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


How reproducible:
for worst result, change apache config, get it wrong, wait for logrotate to try
to restart apache and apply changes then fail at 4am. no service for 5 hours!
(hasn't happened to me yet thank goodness)

Steps to Reproduce:
1.
2.
3.
    
Actual results:
restarts systems daemons

Preferred results:
leave daemons alone

Additional info:

Comment 1 Elliot Lee 2003-01-13 19:24:12 UTC
Daemons have to be restarted in order for logging to continue to work - if apache does not 
get restarted, then there is no logging at all, because the information is being written to old, 
now-deleted logfiles.

To prevent the situation you describe, don't leave the system with an invalid or untested 
configuration.