[mythtv-users] Ticket # 10414

Brian Phillips brian.phillips at byu.net
Fri Nov 16 18:14:48 UTC 2012


Thomas Mashos wrote:
> You don't need to roll your own kernel, it's a simple setting change.
> The Mythbuntu packages have even done this change for you for any
> build in the last 4 months. See
>
https://github.com/MythTV/packaging/commit/524027687b8048815a004cbf8cb9ba06f
552fb72
> 
> Thanks,
> 
> Thomas Mashos

I see.  Looks like my version of Mythbuntu has already enabled that setting
change:

root at backend:/etc/sysctl.d# cat 30-mythtv-sysctl.conf
# Increase the max allowed socket buffer for MythTV.
#   See http://code.mythtv.org/trac/ticket/10414 for more context
# Doesn't actually increase the default socket buffer so it shouldn't affect
#   any other applications.
net.core.rmem_max=1048576
root at backend:/etc/sysctl.d#

So, still getting bad recordings.  Ticket closed prematurely?  Again, the
closer said it would be controversial.  The explanation given in the ticket
really didn't account for all the folks who had working systems upon rolling
back to 0.24.

If I knew the problem was corrected in 0.26, I would definitely spend some
time getting my system there.  But the ticket was closed, milestone removed,
and priority set to "minor" which doesn't give me hope this was ACTUALLY
looked at in-depth in order to be solved for 0.26.  Something that's
resulting in consistently corrupted recordings makes me wonder if "minor" is
really the appropriate classification.  Recording TV is kinda the main point
of a DVR software, no?



More information about the mythtv-users mailing list