[mythtv] Overlapping calls to readSocket

[Ramon Redondo]

> > , and not with absolute current CVS - About 2 hours before Isaac's "More
> > locking for the sockets" checkin.
> 
> Thank you very much. This was very helpful.
> 
> > Also, is it really necessary to:
> > 2005-04-13 02:31:17.632 54 BACKEND_MESSAGE[]:[]RESCHEDULE_RECORDINGS -1[]:.
> > ..
> > 2005-04-13 02:31:20.638 54 BACKEND_MESSAGE[]:[]RESCHEDULE_RECORDINGS -1[]:.
> > ..
> > 2005-04-13 02:31:23.849 54 BACKEND_MESSAGE[]:[]RESCHEDULE_RECORDINGS -1[]:.
> > ..
> >
> > Quite so often? Surely once per second (or, preferably, 30 seconds)
> > would be better?
> 
> The "-1" request is to rebuild all the schedule info from scratch.
> This should only happen when the master backend starts up and once
> after each run of mythfilldatabase. If this is the EIT parser as
> Mark Edwards suggests, that strategy should be reconsidered to only
> update once after there is a new set of data.
> 
> --  bjm

Back when DataDirect was first implemented into a released version of
MythTV, I remember seeing something like this.  I think I had set my
start and end time options to be an hour apart or something like that.
 As a result, for that entire hour, MythFillDatabase ran continuously,
I think every minute.  When I fixed my DD settings, the problem went
away.

I'm not sure if this is related, and it was so long ago, I don't
remember how I had gotten into that state.  But if this is the same
thing, then you could check the logs to see if mythfilldatabase is
running over and over again.