#13593: Python: Use 'MasterServerName' instead of 'MasterServerIP'
-----------------------------------+--------------------------
Reporter: rcrdnalor | Owner: rcrdnalor
Type: Patch - Bug Fix | Status: assigned
Priority: minor | Milestone: needs_triage
Component: Bindings - Python | Version: Master Head
Severity: medium | Keywords:
Ticket locked: 0 |
-----------------------------------+--------------------------
Ticket #13024 : Networking Improvements introduced new settings
for '!MasterServerName', '!BackendServerAddr' and '!BackendServerPort'
and deprecates '!MasterServerIP' and '!MasterServerPort'.
'!BackendServerAddr' can be an IPv4 or IPv6 in the classical
"dot/colon" notation, or is provided in it's canonical form.
{{{
From settings table:
| value | data | hostname |
+-------------------+---------------------+----------+
| BackendServerAddr | 192.168.1.100 | myserver |
| BackendServerPort | 6543 | myserver |
| MasterServerName | myserver | NULL |
+-------------------+---------------------+----------+
or
| value | data | hostname |
+-------------------+---------------------+----------+
| BackendServerAddr | server.example.com | myserver |
| BackendServerPort | 6543 | myserver |
| MasterServerName | myserver | NULL |
+-------------------+---------------------+----------+
}}}
Thanks to Ross Boylan for pointing this out in the user mailing list and
to and to Peter Bennett for additional explanation.
The workaround until this ticket gets fixed is to use only
IP addresses in the ".dot" notation and take care, that the
"!MasterServerIP" is identical to the "!BackendServerAddr".
Attached patch uses these new settings for the Python Bindings
instead of the deprecated ones.
--
Ticket URL: <https://code.mythtv.org/trac/ticket/13593>
MythTV <http://www.mythtv.org>
MythTV Media Center
-----------------------------------+--------------------------
Reporter: rcrdnalor | Owner: rcrdnalor
Type: Patch - Bug Fix | Status: assigned
Priority: minor | Milestone: needs_triage
Component: Bindings - Python | Version: Master Head
Severity: medium | Keywords:
Ticket locked: 0 |
-----------------------------------+--------------------------
Ticket #13024 : Networking Improvements introduced new settings
for '!MasterServerName', '!BackendServerAddr' and '!BackendServerPort'
and deprecates '!MasterServerIP' and '!MasterServerPort'.
'!BackendServerAddr' can be an IPv4 or IPv6 in the classical
"dot/colon" notation, or is provided in it's canonical form.
{{{
From settings table:
| value | data | hostname |
+-------------------+---------------------+----------+
| BackendServerAddr | 192.168.1.100 | myserver |
| BackendServerPort | 6543 | myserver |
| MasterServerName | myserver | NULL |
+-------------------+---------------------+----------+
or
| value | data | hostname |
+-------------------+---------------------+----------+
| BackendServerAddr | server.example.com | myserver |
| BackendServerPort | 6543 | myserver |
| MasterServerName | myserver | NULL |
+-------------------+---------------------+----------+
}}}
Thanks to Ross Boylan for pointing this out in the user mailing list and
to and to Peter Bennett for additional explanation.
The workaround until this ticket gets fixed is to use only
IP addresses in the ".dot" notation and take care, that the
"!MasterServerIP" is identical to the "!BackendServerAddr".
Attached patch uses these new settings for the Python Bindings
instead of the deprecated ones.
--
Ticket URL: <https://code.mythtv.org/trac/ticket/13593>
MythTV <http://www.mythtv.org>
MythTV Media Center