--=_courier-6484-1045484162-0001-2
Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1
Content-ID: <Pine.LNX.3.96.1030216205709.29049D@gatekeeper.tmr.com>
Content-Description: signed data
On Sun, 16 Feb 2003, I wrote:
> > I've got NFS problems with 2.5.5x - 60-bk3, too, but here I can workaround
> > them by simply pinging the NFS-server every second... Funny, but it works!
> > Perhaps this can help finding the real bug?!
[ let's try this again, not typing in a moving car ]
> I was looking for network issues when I started timing pings, and didn't
> see any. I thought it was bad timing, like not raining when you have a
> coat, but maybe I was curing it.
Since it's possible that pings will actually change the problem rather
than measure it, I'll tcpdump for a while and see if that tells me
anything. I suspected network problems, since tcp has priority over udp in
some places.
I looked at the code last night, but I don't see anything explaining a
ping making things better. Something getting flushed?
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.--=_courier-6484-1045484162-0001-2 Content-Type: application/pgp-signature; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-ID: <Pine.LNX.3.96.1030216205709.29049E@gatekeeper.tmr.com> Content-Description: signature
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQA+TMCpYAiN+WRIZzQRAkV8AJwKY8v7t1jvBMFbyNXaFt1c5QzKbQCdFcXB /KQsXPQPTki+B5HzH3QsQZc= =PNko -----END PGP SIGNATURE-----
--=_courier-6484-1045484162-0001-2--