Hi Steve,
And remeber
correctly you did! My hostname in /etc/hosts was different
than the actual hostname reported. Edit file, reboot, and Wooo Hooo
dssi land has arrived. Thasnk for all the help guys.
OK, I had hoped that the fix in the latest version would actually make
this case work for the local case. Maybe we should ship some testcode to
spot this case and warn people?
I was assuming he was still using liblo 0.15 - the 'local case' should
work in 0.16. In the scenario that the name resolution setup is *really*
screwed (empty hosts file, no/misconfigured dns), liblo's fallback on
hostname 'localhost' (which then can also not be found) will only work
if liblo clients connect explicitly using the loopback IP address
instead of the default 'localhost'. In that case a warning might be
appropriate.
Cheers,
Walco