27 Jan
2005
27 Jan
'05
11:16 a.m.
On Thu, 27 Jan 2005 14:28:42 +0000, Steve Harris
<S.W.Harris(a)ecs.soton.ac.uk> wrote:
On Thu, Jan 27, 2005 at 12:41:05 +0100, Walco wrote:
Just for the record. The original segfault was using 0.15 (downloaded
from tarball on saturday). The segfaults went away with 0.16 (out of
CVS), but I had no gui until I fixed my hosts file.
Also I dont really thinkg my networking was really in that bad of a
state. (at least from my persepctive). Both wireless and wired
connections work great with a dhcp server and other apps that really
heavily on a network connection (Pure data being the one I use most)
also work well.
m.
Hi Steve,
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.
I have considered that, but the problem is that there is more than one
loopback address. I'm taking the poistion that liblo wont work if your
networking setup is too deeplytruely mangled. 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?