Opened 18 years ago
Closed 18 years ago
#1437 closed patch (fixed)
MythContext::LogEntry drops too many details
| Reported by: | Robert Tsai <rtsai1111> | Owned by: | Isaac Richards |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | head |
| Severity: | low | Keywords: | |
| Cc: | Ticket locked: | no |
Description
MythContext::LogEntry? attempts to achieve a certain amount of syslog-like brevity for repeated messages. However, some messages lose too much information. For example, if you have two recordings beginning/ending at the same time on a multi-tuner system, only the first one gets logged; the second one is logged as "Last message repeated x times: Finished recording".
This patch adds details to the logging. It shouldn't affect the messages this was targeted at ("running housekeeping", etc.), since those often don't provide any "details" anyway.
Attachments (1)
Change History (2)
Changed 18 years ago by
| Attachment: | mythtv.logentry.diff added |
|---|
comment:1 Changed 18 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
(In [9388]) Fix bug causing MythContext::LogEntry? to drop too many details when trying to eliminate multiple consecutive duplicate messages in the logs. Very loosely based on a patch by Robert Tsai. Closes #1437.