[mythtv] [mythtv-commits] Ticket #7542: mythtv-setup should not use LocalHostName
Michael T. Dean
mtdean at thirdcontact.com
Wed Nov 11 18:36:53 UTC 2009
On 11/11/2009 08:03 AM, MythTV wrote:
> #7542: mythtv-setup should not use LocalHostName
> Comment(by anonymous):
> In fact running mythtv-setup on "pc", the slave backend is not a problem
> in my case, since it's also the machine being named as LocalHostName in my
> .mythtv/mysql.txt file. It's going to other machines and running mythtv-
> setup that's a problem.
> Just to confirm that I understand your explanation, you say that I first
> log in to the master backend, "pvr" and run mythtv-setup, yes? Once done
> there, I then log into the slave backend, "pc" and run mythtv-setup there,
> yes? IOW, run mythtv-setup on the backend machine you want to configure,
> If that's the case, then that's exactly the use case for the bug I am
> pointing out here.
> It seems to me that the right thing to do here is for mythtv-setup to
> ignore the LocalHostName value and always configure for the host that it's
> being run on.
mythtv-setup can only identify the installed capture devices and
enumerate their inputs and verify storage locations if it's run on the
machine that's being configured.
There's a plan for a major rework of settings/setup that may allow you
to do some of what you want--i.e. configure things without having to run
mythtv-setup directly on the host you're configuring (at least for the
More information about the mythtv-dev