[mythtv-users] everyday i have to make sure myth worked the day before

Michael T. Dean mtdean at thirdcontact.com
Wed Apr 20 21:03:31 UTC 2011

On 04/20/2011 09:00 AM, Mark Lord wrote:
> On 11-04-20 12:24 AM, Michael T. Dean wrote:
>> When the socket issues first started happening--they seemed to come out
>> of nowhere as people started upgrading their systems to newer libraries
>> or kernels or something--they were very common on most systems.  Then
>> Daniel K rewrote the socket code, and this solved the issue for the
>> majority of users.  Unfortunately, the issue still occurs for some
>> users.  Because the issue is very system/timing/... dependent, we
>> haven't found a way for someone who hasn't been seeing the issues to
>> reproduce them.  Therefore, it is going to be /very/ difficult for
>> anyone to fix until someone who actually sees the problem can diagnose
>> (and/or fix) it.
> Give me some pointers to the files/functions containing the revamped
> socket code, and I'll go through it looking for ways to improve
> robustness and recovery from situations like this.

Mark K reviewed the backtrace on the ticket, and it looks like the 
backend may actually be deadlocked, so I was wrong.


More information about the mythtv-users mailing list