Bug 915246

Summary: Logrotate config missing
Product: [Fedora] Fedora Reporter: Jan Synacek <jsynacek>
Component: numadAssignee: Jan Synacek <jsynacek>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jsynacek, simon.matter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 913546 Environment:
Last Closed: 2013-10-03 13:02:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 913546    
Bug Blocks:    

Description Jan Synacek 2013-02-25 09:47:37 UTC
+++ This bug was initially created as a clone of Bug #913546 +++

Description of problem:
Numad by default logs to /var/log/numad.log and it seems it doesn't care have to clean it up.

Version-Release number of selected component (if applicable):
numad-0.5-8.20121015git
How reproducible:
Always

Steps to Reproduce:
1. service numad start
2. watch /var/log/numad.log
3.
  
Actual results:
The file just grows and grows.

Expected results:
Logrotate should handle it like other log files.

Comment 1 Fedora End Of Life 2013-04-03 19:27:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19