[mythtv] Ticket #10279: spamming logs with shutdown messages

David Engel david at istwok.net
Fri Jul 6 19:01:18 UTC 2012


On Fri, Jul 06, 2012 at 10:00:23AM -0700, Gavin Hurlbut wrote:
> On Fri, Jul 6, 2012 at 9:53 AM, George Nassas <gnassas at mac.com> wrote:
> > I took a quick look and it's obvious what's going on - the test for a
> > countdown event is on line 2809 of scheduler.cpp and it merely checks that
> > the seconds since idle is divisible by 10. If the surrounding
> > method, Scheduler::HandleIdleShutdown, gets called more than once per second
> > and it aligns with that magic 10 interval you'll see multiple events/logs.
> > 264 in the OP's description and that matches my experience.
> >
> > It's easy enough to add an extra condition to line 2809 but it's not clear
> > to me if it's a good idea to hammer HandleIdleShutdown so much. That's a
> > call for the big guns.
> 
> Hahaha.  We had the same for the logging heartbeats that got hammered
> on leap-second-day...  I added protection in there for pretty much the
> same thing.  If someone else doesn't take it, I'll go fix that for ya.
>  Amazing how little things can make such a difference.

Gavin, it's assigned to me, but you can have it as I've only glanced
at the problem so far.  The big question for me is why are we going
through the doRun loop so quickly.  We should be sleeping for 1 to 60
seconds most of the time at the top of the loop.

David
-- 
David Engel
david at istwok.net


More information about the mythtv-dev mailing list