[lkml]   [2000]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: why am i seeing a ~60-second network connection delay with 2.4.0test*?
On Mon, Sep 04, 2000 at 04:00:41PM -0400, Ricky Beam wrote:
> On Mon, 4 Sep 2000, John Kennedy wrote:
> > 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("")}}, 16) = 56
> > poll([{fd=3, events=POLLIN}], 1, 5000) = 0
> port 111 is the rpc portmap. My guess is you aren't running portmap and
> your /etc/nsswitch.conf has "nis" and "nisplus" references in it. (Damn you
> redhat and glibc.)
> This was hashed about long ago. I think it's documented somewhere. I
> usually remove all the damned NIS/NIS+ BS from the system configuration
> (including the libraries) after installing the system. (I have _one_ machine
> with NIS capabilities as it was once integrated into the office network.)

I don't even *have* an /etc/nsswitch.conf (or /etc/host.conf) file.
I thought that would make me safe and predictable, but perhaps not. (:
I also figured a glibc issue would be held constant regardless of the
kernel rev, but that is looking like a bad assumption.

I need to play with glibc anyway because of all the security foo, so
I think I'll beat on that angle a bit.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.061 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site