[mythtv-users] Talking to more than one backend

[Bruce Markey]

Brad Templeton wrote:
> Just a wishlist feature.  After giving a mythtv box to family, I
> want to be able to maintain it.  I can make a tunnel and run mythweb,
> or even phpmyadmin.  
> 
> But I don't want to run mythfrontend remotely for a couple of reasons.
> A big x application can be slow over a remote link, and since my screen

Why would you want to do that? The frontend can be run locally
and just needs to know which DB to connect to through mysql.txt.
Assuming you can resolve hostname and have enough bandwidth to get
string lists even if you can't play video, you can set per host
preferences just like any local frontend.

> is the same size, it will do the annoying resizing of all the graphics
> once for me and then once for them, unless I set my screen to their
> exact size.

Just use the same theme and size as your local system for your
frontend prefs when connected to their db. Besides. when you
run a local process, mythfrontend gets the graphics for the
theme from the local path (/usr/local/share/mythtv/themes/)
and not over the net.

> A couple of options that might make this nice:
> 
>     a) Command line options on mythfrontend to say which backend to talk
>        to, or perhaps more simply, which mysql.txt file to use to say which

The files is searched for in . , $HOME/.mythtv/ then
/usr/local/share/mythtv or where ever it was installed. I have
several test DBs on different machines so I've created per
hostname directories in my home dir, each with a mysql.txt for
that host. I cd into the directory then run any executable
(usually mythbackend, mythfrontend or mythfilldatabase).
"mythconverg" is a variable that only exists in mysql.txt so
you can even have a different database name in the same mysql
server instance then a dir with the mysql.txt to connect to
that DB.

--  bjm