[mythtv-users] 0.25 - livetv fails when starting on a specificchannel

Michael T. Dean mtdean at thirdcontact.com
Mon Mar 19 19:24:35 UTC 2012

On 03/19/2012 03:14 PM, Scott and Nicole Harris wrote:
>>>> That's interesting.  I have one FE that will not play live TV without
>>>> AlwaysStreamFiles turned ON (it just hangs at a blank screen for ~10
>>>> seconds, then the "error opening jumpfile") and have never figured out why.
>>> Almost definitely NFS misconfiguration, as Daniel mentioned.
>>> http://www.mythtv.org/docs/mythtv-HOWTO-23.html#ss23.8 (specifically the
>>> actimeo option).
>>>> About the only thing I can think of is this FE is also a SBE (though that is
>>>> now turned off in favor of mythjobqueue) and it has identical folders
>>>> mounted to the the MBE to allow it to do transcodes.  Maybe something to do
>>>> with that?
>>>> It's also a little concerning that the setting itself has been removed from
>>>> Myth settings screens (I believe it was gone in 0.24 too,but don't quote me
>>>> on that), but it still seems to have a pretty big impact.
>>> The setting was removed because it's a broken setting that was used to
>>> work around system misconfiguration.
>>> If you want mythbackend to stream files, you should ensure the file
>>> system on which those files exist is not mounted locally.  If you want
>>> mythfrontend to read files "locally", you should ensure the file system
>>> on which those files exist is mounted locally.
>>> Or, put another way, if you want to use NFS, use NFS.  If not, don't.
>> There is absolutely no reason to mount a file system locally using NFS
>> if you don't have mythfrontend reading files for playback over NFS.
> How about to allow that machine to do transcode jobs that it didn't record via mythjobqueue?  Which is why I have them mounted locally.

Yes.  That is a reason to have an NFS mount (all MythTV 
"recorders"--including transcoders--need to be able to write directly to 
the file system, so you can use NFS to make that file system available 
on a remote system).

However, a properly configured NFS mount is usable for /both/ playback 
and transcoding.

I.e. there's no reason to use NFS for transcoding but not use NFS for 
playback.  Therefore, you don't need to force MythTV protocol streaming 
from the backend for playback.  Just let it use the NFS-mounted file 
system directly.


More information about the mythtv-users mailing list