Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#7542 closed defect (invalid)

mythtv-setup should not use LocalHostName

Reported by: brian@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: MythTV - Mythtv-setup Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no

Description

If I have a LocalHostName? setting in my .mythtv/mysql.txt file and it's set to, say, "pc", and I log into a backend machine called, say, pvr as my own account and run mythtv-setup there, it should not store the settings for that backend with the "pc" machine name but should use the name of the machine the backend is running on.

Change History (5)

comment:1 Changed 10 years ago by Nigel

There is a reason for this - slave backends. MythTV allows multiple machines to run a backend. The way to setup "pc" as a slave backend to "pvr" is to run mythtv-setup on it, and configure all the database stuff to that mythbackend can properly run on "pc".
Brian, this isn't really a defect and should be closed, but I will humour you and perhaps add a warning popup when mythtv-setup is run on "pc".

comment:2 Changed 10 years ago by Dibblah

Resolution: invalid
Status: newclosed

There is no (easy) way to implement this behavior. As nigel notes, any machine could run a backend. There are also valid reasons for running mythtv-setup on a non-recording backend - To define storage groups available on that machine for example.

comment:3 in reply to:  1 Changed 10 years ago by anonymous

Replying to nigel:

There is a reason for this - slave backends. MythTV allows multiple machines to run a backend.

Of course. I even run multiple backends here, with "pc" as a slave, so I understand the use-case succinctly. But I think this is orthogonal to the actual problem...

The way to setup "pc" as a slave backend to "pvr" is to run mythtv-setup on it, and configure all the database stuff to that mythbackend can properly run on "pc".

Indeed. That is in fact exactly what I did/do. But that's not really the bug/issue I am pointing out here.

Brian, this isn't really a defect and should be closed, but I will humour you and perhaps add a warning popup when mythtv-setup is run on "pc".

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, yes?

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.

comment:4 in reply to:  2 Changed 10 years ago by anonymous

Replying to Dibblah:

There is no (easy) way to implement this behavior. As nigel notes, any machine could run a backend. There are also valid reasons for running mythtv-setup on a non-recording backend - To define storage groups available on that machine for example.

Indeed. I don't disagree with any of that. What I am saying though is that the LocalHostName? value in my ~/.mythtv/mysql.txt file should be ignored by mythtv-setup because if it's not, I end up writing configurations to the database for the machine named in LocalHostName? and not the machine that mythtv-setup is being run on/configured for.

comment:5 Changed 10 years ago by sphery

The OP was setting the LocalHostName? override in $HOME/.mythtv/mysql.txt with a shared HOME directory used by multiple hosts but wanted the functionality of mythtv-setup without the override. Solution was to just remove the override from mysql.txt. Details in thread at http://www.gossamer-threads.com/lists/mythtv/users/407180#407180

Note: See TracTickets for help on using tickets.