Opened 13 years ago
Last modified 13 years ago
#9365 closed Bug Report
mythfrontend logging allows over 32 log entries per millisecond, rapidly filling hard drive — at Initial Version
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - General | Version: | 0.24-fixes |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
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.
$ mythfrontend --version Please attach all output as a file in bug reports. MythTV Version : df2d58b MythTV Branch : fixes/0.24 Network Protocol : 63 Library API : 0.24.20101129-1 QT Version : 4.6.2 Options compiled in: linux debug using_alsa using_jack using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_directfb using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg
Note: See
TracTickets for help on using
tickets.