That means that changes made in the 'old' conf. Also note that the individual. Just be sure that there aren't any other. Jump to: navigation , search. Category : Advanced Topics. Navigation menu Personal tools Log in. Namespaces Page Discussion. Views Read View source View history. This page was last modified on 14 January , at In most cases, the cause is that different config. For example, if the backend is started by user mythtv but the frontend is started as the login user AND they have separate config.
Great question and there's a simple answer. Look in the log file for the program being run. There will be a line containing text similar to this:. This is a bit harder. That's not too bad, but here's the hard part. It's not unusual for distributions to alter the environment in init service, configuration or scripts that start the mythbackend.
The same is true for things that start mythfrontend. Here are some specific examples of files used to start mythbackend at boot time:. The 4th is there because it's use has been observed in the wild, but doesn't seem to be very common. Finding the location of where mythfrontend sets the environment needs to be added.
Paste the command line here if that doesn't work. All rights reserved. Other names may be trademarks of their respective owners. Also, unless you've changed the default name of the database, mythtvconverg should be mythconverg. The database is indeed mythconverg The password I tried is that in config. Note that the login root user and MySQL root user have nothing to do with each other.
The MySQL root password is likely different from the login root one. You or your distribution would have created it. Don't bother with anything else 'til that's done. If you look at mc. Board index All times are UTC.
0コメント