[mythtv-users] ticket 10504 and php-5.4.8-1.fc17.x86_64

[Michael T. Dean]

On 12/12/2012 10:23 AM, Udo van den Heuvel wrote:
> On 2012-12-10 23:02, Bill Meek wrote:
>> On 12/10/2012 01:19 AM, Udo van den Heuvel wrote:
>>>> Please paste the mysql output. I don't understand what you
>>>> mean by "multiple line".
>>> The database has a set of BackEndIP lines for both recorder and
>>> localhost.
>> Thank you for explaining.
>>
>> That means that at some time your hostname was "localhost" and at some
>> other time it was "recorder".
>>
>> Now, hostname is returning "recorder.hierzo", and database lookups that
>> match
>> on that hostname won't be found. That's the cause of your backend's
>> failure to start. I understand that you solved the problem by using the
>> <LocalHostName>  line in config.xml.
> Correct.
> recorder was an alias to localhost which is not correct.
> So I added a correct entry for the ip at eth0 with the full name and the
> alias.
>
>> As to your follow up post; yes I read that code and I agree that the
>> LOG_NOTICE, "Empty LocalHostName." should be better.
> For only the case of an actually empty LocalHostName.
> For one that cannot be bmatched against /etc/hosts or one taht is the
> default, whatever that may be at any time, a different error should be
> produced.

No.  The "LocalHostName" has no relationship, whatsoever, to a host 
name.  It is just a profile identifier used to say which settings, 
configuration, etc., this application should use on this system.  It's 
using a less-than-ideal name (that will be changed when other, 
more-important things are completed) because the default value used for 
the profile identifier is the host name (as that's something a user is 
likely to be able to relate to a specific machine in the MythTV 
system--as opposed to some non-human-friendly value, such as a UUID), so 
when it was named (many, many, many years ago), the name "LocalHostName" 
seemed a reasonable name for it.

>> The logic is fine.
> I doubt that.
> Silently interpreting a default string as empty if not logical in any way.
> A default name could be interpreted as an unconfigured system, so yell
> about that instead.

That "default" LocalHostName ("my-unique-identifier-goes-here") is /not/ 
a default.  It is a sentinel value that specifically means, "no 
specified value".  It is the one and only disallowed value for the 
LocalHostName profile identifier.

Mike