Date: Mon, 05 Apr 2004 13:10:50 -0700 From: Eli Dart <dart@nersc.gov> To: Brandon Erhart <berhart@ErhartGroup.COM> Cc: freebsd-net@freebsd.org Subject: Re: FIN_WAIT_[1,2] and LAST_ACK Message-ID: <20040405201050.D5B2EF8F2@gemini.nersc.gov> In-Reply-To: Message from Brandon Erhart <berhart@ErhartGroup.COM> <6.0.2.0.2.20040405133109.01c755c8@mx1.erhartgroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-1956043834P Content-Type: text/plain; charset=us-ascii In reply to Brandon Erhart <berhart@ErhartGroup.COM> : > Well, I responded to the group that I had taken one of the fellows advice > posting here, and modified the tcp_usrclosed in netinet/tcp_usrreq.c. I understand that -- I was trying to discover if you'd come across something that needed a more general fix (see note from Mike Silbersack). If your application can't wait for whatever the standard timeout is, that's fine -- you've got your fix, and you're good to go. However, if there is a problem with connections hanging out forever in the process of closing, that something that might be good to look at independently. So, do you remember how long the "problem connections" were sticking around in FIN_WAIT_? or LAST_ACK? Are we talking seconds, minutes, hours, days? Thanks, --eli > > So all is well -- it gets TCPS_CLOSED state and the tcps_close() function > called on the tuple IMMEDIATELY. It doesn't switch states depending on > which state the connection is currently in. I also made a sysctl variable > for it (to turn the "feature" on or off), and will post the small patch > along w/ some other small changes I have made soon. > > Thanks, > > Brandon > > At 11:17 AM 4/5/2004, you wrote: > > >In reply to Brandon Erhart <berhart@ErhartGroup.COM> : > > > > > Hello everyone, > > > > > However, I have run into a new problem. I am getting a good amount of > > > blocks stuck in FIN_WAIT_1, FIN_WAIT_2 or LAST_ACK that stick around for a > > > long while. > > > >Could you define "long" in this case? Are we talking about 60 > >seconds, or 60 minutes? I get the feeling that your requirements > >might make your perception of "long" different from others' notion of > >"long." > > > >The reason I ask is that there was a bug once upon a time that made > >some connections stick in LAST_ACK forever.... > > > > --eli > > > > > > > --==_Exmh_-1956043834P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) Comment: Exmh version 2.5 07/13/2001 iD8DBQFAcb1KLTFEeF+CsrMRAioFAJ4t/qpNiTuq1oIBXJBeKhpsFJp2vACdEm4p mHfzleA1edTD8cE1d70U744= =Tqw9 -----END PGP SIGNATURE----- --==_Exmh_-1956043834P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040405201050.D5B2EF8F2>