On Thu, 4 Nov 1999, Kenneth D. Merry wrote:
>
> Before I spend a lot of time hunting this down, I figured it might be worth
> asking -- is there any particular reason why TCP sockets may be getting
> stuck in the CLOSING state more often now?
>
> I upgraded a machine from -current as of about June 26th to -current as of
> last Friday (October 29th), and I've got an ever increasing number of
> sockets stuck in the CLOSING state:
>
> Active Internet connections
> Proto Recv-Q Send-Q Local Address Foreign Address (state)
> tcp 0 0 myhost.1929 othermailserver1.auth CLOSING
> tcp 0 0 myhost.1904 othermailserver1.auth CLOSING
....
> tcp 0 0 myhost.1609 othermailserver1.auth CLOSING
>
> This didn't seem to happen with the previous version of -current. I looked
> through the commitlogs for the TCP code, and I saw some timer changes, but
> nothing that looked like it would obviously have this effect.
>
> Anyone have any ideas?
<aol> me too! </aol>
Needed to reboot to allow something to bind to the socket.
Ie. happening to server side sockets.
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
