[mythtv-users] mythtv-setup without UPNP searching for backend?

Paul Harrison mythtv at mythqml.net
Wed Jan 12 01:55:21 UTC 2022

On 12/01/2022 01:16, James Abernathy wrote:
> On Tue, Jan 11, 2022 at 4:48 PM James <jam at tigger.ws 
> <mailto:jam at tigger.ws>> wrote:
>     > On 11 Jan 2022, at 8:30 pm, Stuart Auchterlonie
>     <stuarta at squashedfrog.net <mailto:stuarta at squashedfrog.net>> wrote:
>     >
>     > On 09/01/2022 17:00, James Abernathy wrote:
>     >> When I'm working on building a test mythtv BE/FE combo to test
>     something, I have mythtv-setup fail due to it finding another
>     backend like my production one. The only way I've found to recover
>     from this is reformat the HD and start over with O/S install.  I
>     know that you could spend a year or so digging into what files
>     need to be removed, but I can't find them all so in the interest
>     of time, I just start over.
>     >> What I'd like is a way to tell mythtv-setup to not go looking
>     for anything, just stay on localhost and make all assumptions as
>     localhost.  Does that exist??
>     >
>     > If you override the environment variable MYTHCONFDIR to a different
>     > directory, then the you can separate out the configuration data
>     between
>     > dev/test/prod instance even on the same machine.
>     >
>     > start with MYTHCONFDIR pointing to an empty dir, and then run
>     > mythtv-setup and start from the beginning.....
>     >
>     > You will probably need to let it timeout on the search, and then
>     select
>     > manual setup.
>     Stuart that does not answer the question. IE fresh install
>     mythtv-setup - ooops
>     I've got a new machine I want to play with.
>     I don't want that machine messing up my master db.
>     I don't want that frontend talking to or displaying recordings
>     from the 'real' master backend
>     I don't want that backend to be a slave.
>     Great Myth: I do not have any fire wall in my network. The only
>     port forward is ssh. Bad Guys can reach my modem then do nothing.
>     It violates RFC to route private IPs.
>     So every router between bad guys and me needs to be broken AND my
>     modem need to be broken for Bad Guys to get to me. So a flaw
>     allows them to get to me, why is a fire wall going to help.
>     [firewalls do stop infected windows machines from calling OUT]
>     The only solution that works for me is to firewall the play
>     machine (and you can do wonderous stuff eg a play frontend machine
>     and a play backend. With ssh tunnels you can create magic,
>     As an alternative to Stuarts MYTHCONFDIR suggestion I use a
>     .mythtv_a .mythtv_b and an alias (a mv .mythtv_a .mythtv) to
>     switch a front end (same version) from real to play.
>     I've not tried, and mac with their bundle system make it trivally
>     easy, to run 2 frontends say a 31 and a 32,
>     Building mythtv with different PREFIX would work together with the
>     alias solution
>     James
> What would make the connection of a Frontend to a backend easier the 
> first time is when you select Search, it should show more data.  There 
> is no difference in the list of the backends unless they are on 
> different versions of Mythtv? If it could show the IP address or 
> something else unique that would help
> JIm A

What I do is create a new devicemaster.xml so I can tell which backend 
is which.

Some basic instructions here on the UPnP page in the wiki "Overriding 
the default devicemaster.xml file" section.


Paul H.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220112/ce1d34df/attachment.htm>

More information about the mythtv-users mailing list