On Mon, Sep 04, 2000 at 08:04:49AM +0200, Martin MaD Douda wrote:
> I'm using 2.4-test since it was born and never saw this behavior. Could
> you please strace and ltrace your ping so we can see where it waits?
Can't find source for ltrace, but I have strace.
Ping seems to be spending its time in a sendto()/poll() loop:
sendto(3, "U\3Z\241\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3\0"..., 56, 0, {sin_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("127.0.0.1")}}, 16) = 56
poll([{fd=3, events=POLLIN}], 1, 5000) = 0
That output was from `strace ping -c1 -n 132.241.60.33'. This
particular ping is from inet6-apps-0.35, FYI.
I can't find sourcecode that does exactly that part, so I'm going to
have to write a little test program and see if some bit of OS
misconfiguration is causing problems when run under 2.4.x. In any case,
I've attached a strace for both ping and telnet that hangs up for a
while doing the same kind of looping.
Telnet was from inetutils-1.3.2, FYI.
Is looks like it might be trying to talk to the portmapper for some
reason. I don't have the portmapper running on either kernel version.
It is going to take me a bit to make a non-pcmcia system to hop back
and forth between 2.2.x and 2.4.x, but I thought I would spit that out.
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:18 EST