+++ 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.
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
Upstream commit: https://git.fedorahosted.org/cgit/numad.git/commit/?id=b621838bf9c8203e87137eca28e19bcc381cde2a