Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!melpar!toppin
From: toppin@melpar.UUCP (Doug Toppin)
Newsgroups: comp.protocols.tcp-ip
Subject: TCP/IP close connection TIME_WAIT ?
Keywords: tcp
Message-ID: <227@melpar.UUCP>
Date: 22 Aug 89 20:14:21 GMT
Distribution: usa
Organization: E-Systems, Falls Church, VA
Lines: 16

We are using IBM Xenix 2 on the PC/AT with Network Research Corp
implementation of TCP/IP (called Fusion) and have hit a snag.
We often get the error EWOULDBLOCK on a heavily used socket (many
opens and closes).  In the Sept. MIPS magazine David Betz writes:
"after a close, the resources used by that connection are not freed
immediately... Since this time interval is in the tens of seconds,
eventually all the resources are tied up in this TIME_WAIT."
My questions are:
* is the time value a constant?
* is it tunable?
* is the value part of the TCP/IP specification?
* is it possible to detect that you are using the last available resource?
* is it possible to allocate more of these resources?
thanks
Doug Toppin
uunet!melpar!toppin