Date: Tue, 28 Sep 1999 18:10:02 -0700 (PDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: freebsd-bugs@FreeBSD.org Subject: kern/14026: Many network connections get left in the 'CLOSING' state Message-ID: <199909290110.SAA47554@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/14026; it has been noted by GNATS. From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: rob@ideal.net.au Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: kern/14026: Many network connections get left in the 'CLOSING' state Date: Tue, 28 Sep 1999 21:01:45 -0400 (EDT) <<On Tue, 28 Sep 1999 16:16:06 -0700 (PDT), rob@ideal.net.au said: > tcp 0 0 proxy1.syd.8080 port19.syd.2197 CLOSING > tcp 0 0 proxy1.syd.8080 port56.cam.1779 CLOSING Sorry, that's Just The Way TCP Works. In particular, this can happen if the client completely disconnects from the network at an inopportune moment.(*) Eventually TCP will send a probe to that address while some other user is connected; when this happens, the other end will reply with a reset and the state for this connection will be zapped. -GAWollman (*)Specifically, CLOSING state is normally entered when: a) the other end requested close before we are ready b) we eventually agree to close c) by which time the other end has gone away It is possible, but unlikely, for CLOSING state to be entered by other means as well. -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909290110.SAA47554>