[mythtv-commits] Ticket #7542: mythtv-setup should not use LocalHostName

MythTV mythtv at cvs.mythtv.org
Wed Nov 11 13:03:00 UTC 2009


#7542: mythtv-setup should not use LocalHostName
-----------------------------------+----------------------------------------
 Reporter:  brian@…                |        Owner:  ijr    
     Type:  defect                 |       Status:  closed 
 Priority:  minor                  |    Milestone:  unknown
Component:  MythTV - Mythtv-setup  |      Version:  unknown
 Severity:  medium                 |   Resolution:  invalid
  Mlocked:  0                      |  
-----------------------------------+----------------------------------------

Comment(by anonymous):

 Replying to [comment:1 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.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7542#comment:3>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list