[mythtv-users] [Q] : how to trace "wait for 2 seconds..." problem

[Aran Cox]

On Tue, Nov 11, 2003 at 06:38:46AM -0500, aaron wrote:
> On Mon, 10 Nov 2003 20:37:54 +0100 spake manu of:
> 
> > 	Hi all,
> > I run into this once a while (sometimes nothing in several days, but  
> > today it hit me twice). How could I trace it to nail down the bug?
> > Just to be precise : the frontend image is stalled, and on the console  
> > I saws these messages "wait for...". I killed muythfrontend (don't  
> > remember if I could just have exited cleanly from it though), and  
> > restarted it, and then it worked.
> > I can place some printf in the code if necessary.
> 
> 
> Hmm, I see this too. For me, it only happens when watching LiveTV. I find that
> I have to kill the frontend; I'm unable to exit cleanly. Simply killing the
> frontend and restarting it is enough to get around the problem; I don't have
> to do anything to the backend.
> 
> It's almost like the backend just suddenly decides to stop sending data to the
> frontend.
> 
> For me, it only seems to happen when I'm watching something interesting. ;)
> 
> I had thought it might have something to do with clock drift (I sync my clock
> every hour... apparently my motherboard clock sucks... ;), but now I'm not so
> sure. Since I've been monitoring it, the sync has not moved more than 1 sec at
> a time, usually less.
> 
> aaron

You should set up ntp, instead of syncing your clock once an hour.  Using ntpd
should take less network resources and keep your clock in sync throughout
the hour.  

Unfortunately, the ntp docs can be intimidating but it's pretty easy to get a 
simple client configuration set up.

Aran

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-users/attachments/20031114/8eef22cc/attachment.pgp