[mythtv-users] localhost errors
Michael T. Dean
mtdean at thirdcontact.com
Fri May 30 17:43:05 UTC 2008
On 05/30/2008 01:01 PM, Mr cctsurf wrote:
>> Each frontend needs to save it's config data in the database, if you
>> just used localhost for all frontends they'd overwrite each other.
>> While in your circumstance it wasn't helpful I dont think this was a
>> recent change...
> I understand that the frontend needs to save it's config data in the database and that it should be catagorized under the hostname, however, that it accesses the local database under the hostname, not the localhost or ip address seems to be new, I've never had this problem in the 5 years I've used myth. I could access the backend from all the other frontends, but the localhost. I couldn't run nuvexport, I couldn't run mythfrontend, I couldn't even run mythtv-setup, yet I could access the database from the commandline. It may be something new with mysql, but I would assume that it is something that should work when working from the localhost.
It's new with your config. /You/ tell Myth what hostname to use to
access the DB. Myth 0.21 has a completely new mechanism for specifying
the hostname/DB connection info (and changes from the old mysql.txt to
the new config.xml). When setting up after the upgrade, you simply
typed your hostname where previously you had typed localhost (or, where
previously, you used the default config file, so you never typed anything).
More information about the mythtv-users