<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">I can tell you that's exactly the same commit/SHA1 I'm running on in
my backend that was experiencing a 7% failure rate. And that now
I'm well over 100 recordings without any failures.
The build I did at v0.27-pre2-583-g031c724 had the fix and I believe
two more. So, if "up until last night" means you did a new build then,
perhaps you're OK now.
You can always: grep 0.27-pre2 /var/log/mythtv/mythbackend* to see what
version you were running (or wherever your logs are kept.)
As to the -dirty, you can always do: git diff to verify that the
changes are the ones in the patch you added.
--
Bill
</pre>
---------------------------------------------------------------------------------<br>
It appears my problem was caused by me. It was related to the<br>
patch I implemented for the backend segmentation faults I was<br>
seeing. I implemented the PATCH in ticket 11318 and while it <br>
stopped the segfaults it also stopped the HDHR from working.<br>
I now have implemented PATCH2 in ticket 11318 and things are<br>
looking much better. Also if this patch causes some other issues<br>
I will implement the patch in ticket 11316 however that patch did<br>
cause some interesting things to happen related to recordings<br>
showing up as zero bytes until I go out of watch recordings and<br>
get back in sometimes several time. So I will be more careful and<br>
read to the end of the ticket before implementing a patch next<br>
time.<br>
Thanks again for all your help.<br class="Apple-interchange-newline">
</body>
</html>