Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!dls
From: dls@mentor.cc.purdue.edu (David L Stevens)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Problem retrying "connect"
Keywords: connect, ULTRIX, tcp
Message-ID: <13457@mentor.cc.purdue.edu>
Date: 30 Aug 90 00:01:07 GMT
References: <1990Aug29.212123.12889@fs-1.iastate.edu>
Reply-To: dls@mentor.cc.purdue.edu (David L Stevens)
Organization: PUCC UNIX Group
Lines: 6


	If memory serves, a failed connect(2) in 4.2 systems would leave
the socket in an unusable state. The fix is to close the socket and start
all over from socket(2). We had this problem once upon a time too...
-- 
					+-DLS  (dls@mentor.cc.purdue.edu)