[mythtv-users] Ticket # 10414
fatgerman at gmail.com
Fri Nov 16 18:26:07 UTC 2012
On Friday 16 Nov 2012 11:14:48 Brian Phillips wrote:
> 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
> > Thanks,
> > Thomas Mashos
> I see. Looks like my version of Mythbuntu has already enabled that setting
> 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.
> 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.
Something I noticed is that that setting appears to be screwing really badly with the performance of my NFS shares and SSH connections to my myth box. Disabling it seems to have cured the problems I was having. I say seems to as it's only been a day, but I've so far noticed none of the regular pauses I used to have during SSH connections or when transferring files via NFS.
> 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?
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users