Bug 102746
Summary: | Logwatch not restricting up2date log range to yesterday | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew Prentice <mprentice> |
Component: | logwatch | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | mprentice |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:58:10 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
Matthew Prentice
2003-08-20 15:58:44 UTC
*** This bug has been marked as a duplicate of 99438 *** I agree this is similar to 99438. However, in this case the Yesterday range is working correctly for all logs except for up2date. It appears in 99438 that the Yesterday range is not working for any of the logs. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |