Bug 170639
Summary: | All old logs are removed with 'dateext', only one without it. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mateus César Gröess <mateuscg> |
Component: | logrotate | Assignee: | Tomas Smetana <tsmetana> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | k.georgiou |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-05-14 11:13:33 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
Mateus César Gröess
2005-10-13 14:35:56 UTC
I think logrotate should ignore "rotate count" when "dateext" option is used, because there is no real log rotation in dateext scenario. Old logs should be left untouched unless maxage is used. Do u agree? I think there is a good number of servers that are running with "dateext" and using "rotate count", not "maxage" to limit the number of logs archived, so ignoring it would cause problems to many system admins. After post this bug report I thought if someone would care about, because it is just a different behavior and "dateext" wasn't doing bad things, but I left the bug untouched to at least document the differences, and see if someone have a good idea to end with these differences and don't confuse sysadmins. There are two options left: 1. Delete the old logs in the scenario without dateext 2. Let it be Personally I'm in favour of 2. -- I just don't see this as a bug. This report seems to be inactive and since I don't think the default behaviour is buggy in any way, I'm closing it. |