Opened 15 years ago
Last modified 15 years ago
#9365 closed Bug Report
mythfrontend logging allows over 32 log entries per millisecond, rapidly filling hard drive — at Version 1
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - General | Version: | 0.24-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description (last modified by )
Just like in ticket #8244 and ticket #8367, ticket #9364 describes the log file being filled up with repeated logs. This most recent is even more aggressive than what I described in the first bug... around 32 entries per millisecond.
Is there any way that the logging function, upon receiving the same message as the previous message, could wait at least a second, if not more, to log an identical message to prevent hyperactive messages like this one from filling up logs in record time?
In under two hours, it has generated 20 GB of logs.
Note: See
TracTickets for help on using
tickets.
attaching as a file, as the text says to