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

[David Engel]

On Fri, Jul 06, 2012 at 03:53:35PM -0700, Gavin Hurlbut wrote:
> On Fri, Jul 6, 2012 at 12:01 PM, David Engel <david at istwok.net> wrote:
> > 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.
> 
> OK, I didn't want to steal it from ya, but if you're busy anyways,
> I'll take a look.  We have had some of these odd timing-related things
> lately, although we can't blame THIS report on the leap second that
> happened a week later, so there's gotta be something in there.  A set
> of new eyes on it may help.

Don't worry.  You're not stealing it.  Heck, I didn't even know it was
assigned to me until I went looking for other deadlock tickets
yesterday.  

Daniel reworked the loop prior to 0.25 to sleep for longer times when
possible.  It used to only sleep for at most 1 second.  The problem is
most likely an unexpected combination of programs at the beginning of
recList or a miscalculation dealing with idle/shutdown times resulting
in a zero or near-zero sleep.  Since it seems to be pretty
reproducible for the people experiencing it, it might be simplest to
put in some extra logging to show how it's calculating the sleep time
and what the result.

David
-- 
David Engel
david at istwok.net