Difference between revisions of "Config.xml"
m (→Template: not sure what this bit is...)
|Line 12:||Line 12:|
Latest revision as of 14:15, 16 February 2014
The file is used multiple times:
- Used by the backend to find the MySQL database - otherweise a built-in default is used: [778249a]cgitgithub
- Used by the frontend to find its backend; otherwise the frontend tries to find a backend using UPnP.
Depending on the program the file is looked up as /etc/mythtv/config.xml or ~/.mythtv/config.xml.
Previously a similar file called mysql.txt was used, which is deprecated since MythTV 0.26.
The following template can be found in mythtv/contrib/config_files/config.xml
<Configuration> <UPnP> <UDN> <MediaRenderer>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</MediaRenderer> </UDN> </UPnP> <LocalHostName>my-unique-identifier-goes-here</LocalHostName> <Database> <PingHost>1</PingHost> <Host>127.0.0.1</Host> <UserName>mythtv</UserName> <Password>mythtv</Password> <DatabaseName>mythconverg</DatabaseName> <Port>3306</Port> </Database> <WakeOnLAN> <Enabled>0</Enabled> <SQLReconnectWaitTime>0</SQLReconnectWaitTime> <SQLConnectRetry>5</SQLConnectRetry> <Command>echo 'WOLsqlServerCommand not set'</Command> </WakeOnLAN> </Configuration>
- The unique name used to look-up host-specific settings. By default the hostname is used, but it can be useful to overwrite this when the hostname is changed or multiple frontends with different configurations should run on the same host.
- The UUID used for the MythTV frontend, when used as a UPnP media renderer.
- These settings are deprecated by the settings below mythtv/libs/libmyth/mythcontext.cpp.
All configuration data is stored in a central MySQL database, which must be reachable for all MythTV components.
- 1=MythTV should try to test-ping the host running the database using ICMP echo-request before actually connecting the database process; usually 1.
- The hostname, IPv4 or IPv6 address of the host, where the database is running.
- The name of the account used to authenticate against the database; usually mythtv.
- The password used to authenticate.
- The name of the schema of the database; usually mythconverg.
- The TCP port number, where the database is running on; usually 3306.
If the database is unreachable, MythTV can try to wake up the host using for example Wake-on-LAN.
- 1=MythTV should try to wake up the host. PingHost=1 must be set as well!
- Seconds to wait between reconnection attempts.
- Number of times to retry; usually 5.
- Command to use to wake server; for example sudo etherwake xx:xx:xx:xx:xx:xx.