[mythtv] Overlapping calls to readSocket

Bruce Markey bjm at lvcm.com
Wed Apr 13 17:11:08 UTC 2005


Allan Stirling wrote:
...
> , 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


More information about the mythtv-dev mailing list