31 May
2008
31 May
'08
9:11 p.m.
Hi all,
I think this is a network setup user error rather than anything
complicated, but anyone know why I get long pauses (5-10secs) when
calling lo_server_thread_new for the first time in a process?
Is it likely to be some timeout I can adjust?
cheers,
dave
1 Jun
1 Jun
7:32 a.m.
Hi Dave,
On Sun, Jun 1, 2008 at 12:11 AM, Dave Griffiths <dave(a)pawfal.org> wrote:
I think this is a network setup user error rather than
anything
complicated, but anyone know why I get long pauses (5-10secs) when
calling lo_server_thread_new for the first time in a process?
I ran into this problem recently too, and I'd love to hear a solution.
There was discussion quite a while ago on the DSSI list about GUIs
being very slow to appear, and lo_server_thread_new was *part* of the
problem. There were suggestions of a network misconfiguration (eg
mistakenly bypassing /etc/hosts and going to the nameserver) and a
possible fix (commenting out the IPv6-style getnameinfo() call in
liblo's src/server.c). This fix works for me, and that suggests that I
have a network configuration problem too.
It might be worth a look:
http://sourceforge.net/mailarchive/message.php?msg_id=20050629170524.GA1632…
http://sourceforge.net/mailarchive/message.php?msg_id=20050709121152.GA1645…
James
--
James McDermott
CS2045,
Dept. Computer Science and Information Systems,
University of Limerick,
Ireland.
www.skynet.ie/~jmmcd
7:41 a.m.
On 1 Jun 2008, at 10:32, James McDermott wrote:
Hi Dave,
On Sun, Jun 1, 2008 at 12:11 AM, Dave Griffiths <dave(a)pawfal.org>
wrote:
Do you have an entry like:
::1 localhost
in your /etc/hosts?
I seem to remember hearing about problems like this before - I think
there's a configure option to disable ipv6, but it seems like a bad
idea to not support it in the 21st century.
- Steve
I think this is a network setup user error rather
than anything
complicated, but anyone know why I get long pauses (5-10secs) when
calling lo_server_thread_new for the first time in a process?
I ran into this problem recently too, and I'd love to hear a solution.
There was discussion quite a while ago on the DSSI list about GUIs
being very slow to appear, and lo_server_thread_new was *part* of the
problem. There were suggestions of a network misconfiguration (eg
mistakenly bypassing /etc/hosts and going to the nameserver) and a
possible fix (commenting out the IPv6-style getnameinfo() call in
liblo's src/server.c). This fix works for me, and that suggests that I
have a network configuration problem too.
7:43 a.m.
On Sun, Jun 1, 2008 at 10:32 AM, James McDermott
<jamesmichaelmcdermott(a)gmail.com> wrote:
possible fix (commenting out the IPv6-style
getnameinfo() call in
liblo's src/server.c). This fix works for me, and that suggests that I
have a network configuration problem too.
Oh -- I've just seen that a newer liblo release (0.24, whereas my
Ubuntu Hardy has 0.23) fixes the problem by disabling IPv6 by default.
What liblo do you have?
James
--
James McDermott
CS2045,
Dept. Computer Science and Information Systems,
University of Limerick,
Ireland.
www.skynet.ie/~jmmcd
4:13 p.m.
New subject: lo_server_thread_new pause (fixed!)
On Sun, 2008-06-01 at 10:43 +0100, James McDermott wrote:
On Sun, Jun 1, 2008 at 10:32 AM, James McDermott
<jamesmichaelmcdermott(a)gmail.com> wrote:
Indeed, simply switching from 0.23 to 0.24 fixes it for me!
Thanks for all the help guys,
cheers,
dave
possible fix (commenting out the IPv6-style
getnameinfo() call in
liblo's src/server.c). This fix works for me, and that suggests that I
have a network configuration problem too.
Oh -- I've just seen that a newer liblo release (0.24, whereas my
Ubuntu Hardy has 0.23) fixes the problem by disabling IPv6 by default.
What liblo do you have? 
7:50 a.m.
On Sun, 2008-06-01 at 00:11 +0100, Dave Griffiths wrote:
Hi all,
I think this is a network setup user error rather than anything
complicated, but anyone know why I get long pauses (5-10secs) when
calling lo_server_thread_new for the first time in a process?
Is it likely to be some timeout I can adjust?
On some Debian systems I've seen this caused by multicast DNS taking a
really long time to fail. In that case I think it helped to remove mdns4
from the hosts: line in /etc/nsswitch.conf.
Of course, no one should be looking up "localhost" using mDNS or any
other form of DNS, so the real error is somewhere else.
--ll
6016
days inactive
6017
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Dave Griffiths -
James McDermott -
Lars Luthman -
Steve Harris