[mythtv-users] mythtv networked setup

[Mark Chou]

OK, bjm (and others), thanks for explaining the networked tuner/storage 
logic.  I had the mythtv "local tuner affinity" working at one time, but in that 
particular instance it turned out my /etc/hosts file was reversed (hosts file 
claimed alice is betty and vice versa).  I corrected that, and the "first free 
tuner affinity" logic you described took place, and I just was no longer sure 
what mythtv networked logic was. 
 
Perhaps in the myth TV documentation there can be brief mention of this, 
and perhaps suggest to folks that they ought to put the largest storage on 
the master backend? 
 
Also, what's the recording storage logic if the master runs (or is about to 
run) out of room?  Is there then "failover" to put the recorded file on the 
second/slave mythtv box? 
 
Also another question while I'm on this topic.  What peer 
"autodiscovery/reconnect" mechanism does the backend use, if any?  If I 
reboot/restart my master backend it seems that my slave backends get 
orphaned, and doesn't seem to want to reconnect to the 
rebooted/restarted master.  In which case I need to restart mythbackend 
on my slave machines to completely restore the myth "virtual cluster." 

______________________________________________________________
Unlimited Internet Access 8.25/Month!
http://www.ivwnet.com/access.html