You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by Chuck Murcko <ch...@hyperreal.com> on 1996/12/24 22:07:10 UTC
cvs commit: apache/htdocs/manual/misc perf-bsd44.html
chuck 96/12/24 13:07:09
Modified: htdocs/manual/misc perf-bsd44.html
Log:
Add reference to FIN_WAIT_2 behavior, and pointer to patch.
Revision Changes Path
1.3 +6 -1 apache/htdocs/manual/misc/perf-bsd44.html
Index: perf-bsd44.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/misc/perf-bsd44.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** perf-bsd44.html 1996/11/21 09:55:50 1.2
--- perf-bsd44.html 1996/12/24 21:07:08 1.3
***************
*** 123,129 ****
necessary at first glance. The reason for this is that if the browser
disconnects in mid-transfer, the socket fd associated with that particular
connection ends up in the TIME_WAIT state for several minutes, during
! which time its mbufs are not yet freed.
<p>
--- 123,134 ----
necessary at first glance. The reason for this is that if the browser
disconnects in mid-transfer, the socket fd associated with that particular
connection ends up in the TIME_WAIT state for several minutes, during
! which time its mbufs are not yet freed. Another reason is that, on server
! timeouts, some connections end up in FIN_WAIT_2 state forever, because
! this state doesn't time out on the server, and the browser never sent
! a final FIN. An example patch for BSDI is available
! <a href="http://www.apache.org/dist/contrib/patches/1.2/fin_wait_2.patch">
! here</a>.
<p>