Bug 247410
Summary: | Logrotate 3.7.4 does not honor size directive | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Seth Robertson <in-redhat> | ||||
Component: | logrotate | Assignee: | Tomas Smetana <tsmetana> | ||||
Status: | CLOSED ERRATA | QA Contact: | |||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 5.0 | CC: | brandon.franks.011, chet.burgess, joel.winteregg, mmalik, ssaux | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHBA-2007-1002 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-11-15 14:07:41 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: | |||||||
Attachments: |
|
Description
Seth Robertson
2007-07-09 04:46:16 UTC
You're right. Thanks for reporting. I didn't see a fix for this issue and since I needed the latest logrotate to address another bug I was encountering I have created a patch for this bug. I have attached a simple fix for this issue. Created attachment 160651 [details]
Patch to address size option not working
This bug is against RHEL, so you have to wait for the next update. If you require a hotfix then you must contact the customer support. *** Bug 251596 has been marked as a duplicate of this bug. *** An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-1002.html *** Bug 448622 has been marked as a duplicate of this bug. *** I am experiencing this bug while using logrotate version 3.8.6. Why is that? |