Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!rice!rice!sun-spots-request
From: tim@ncoast.org (Tim Stradtman)
Newsgroups: comp.sys.sun
Subject: PC-NFS bug
Keywords: Networks
Message-ID: <1990Aug3.002118.3979@rice.edu>
Date: 1 Aug 90 20:36:43 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 25
Approved: Sun-Spots@rice.edu
Originator: spots@titan.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 288, message 10

Has anyone else seen the following problem using PC-NFS:

PC #1 comes up and opens a UDP socket, waits for a packet from anyone
PC #2 comes up and opens a UDP socket, sends id type message
PC #1 replys to the id message, opens a TCP socket, 
      waits for connection from anyone (expects one from PC #2)
PC #2 connects to PC #1
both PCs talk
PC #2 closes the connection
PC #1 goes to sleep for 20 seconds INSIDE the socket close call

The general idea is that PC #1 is acting as a server/gateway, and may have
up to 32 (correction 8 - PC NFS limit :-) sessions running with other
systems. When it hits the close, ALL systems are hung for 20 seconds.
Meanwhile the communications line is missing interrupts, the other users
are hitting ^C and I get calls about slow response.  Sun has filed a "bug
report" - after several months they are "still looking into it".

I would appreciate any help or suggestions.

Thanks
--------
Tim Stradtman
EMAIL to ak215@cleveland.freenet.edu
or post here