httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <m...@hyperreal.com>
Subject cvs commit: apache/htdocs/manual/misc fin_wait_2.html known_bugs.html perf-bsd44.html
Date Tue, 28 Jan 1997 04:23:09 GMT
marc        97/01/27 20:23:09

  Modified:    htdocs/manual  index.html
               htdocs/manual/misc  known_bugs.html perf-bsd44.html
  Added:       htdocs/manual/misc  fin_wait_2.html
  Log:
  Add more information on the FIN_WAIT_2 problem.
  
  Revision  Changes    Path
  1.7       +1 -0      apache/htdocs/manual/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/index.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -C3 -r1.6 -r1.7
  *** index.html	1996/12/10 21:08:15	1.6
  --- index.html	1997/01/28 04:23:05	1.7
  ***************
  *** 39,44 ****
  --- 39,45 ----
    <li><A href="misc/howto.html">How do I? documentation</A>
    <LI><A HREF="misc/security_tips.html">Security tips</A>
    <LI><A HREF="misc/perf.html">Performance hints</a> for heavily loaded
web servers.
  + <LI><A HREF="misc/fin_wait_2.html">Discussion of the FIN_WAIT_2 problem</A>
    </ul>
    
    <!--#include virtual="footer.html" -->
  
  
  
  1.7       +3 -5      apache/htdocs/manual/misc/known_bugs.html
  
  Index: known_bugs.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/misc/known_bugs.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -C3 -r1.6 -r1.7
  *** known_bugs.html	1996/12/24 20:15:47	1.6
  --- known_bugs.html	1997/01/28 04:23:07	1.7
  ***************
  *** 21,31 ****
    <OL>
    
    	<LI>users have reported problems with many connections stuck in the
  ! FIN_WAIT_2 state due to server timeouts. This is an issue with the OS TCP
  ! stack, as some OS never timeout from this state. An example patch for BSDI
  ! is available
  ! <a href="http://www.apache.org/dist/contrib/patches/1.2/fin_wait_2.patch">
  ! here</a>.
    
    	<LI>hard_timeout() for request reads uses incorrect logic, and
    ends up waiting for an initial request read for the default "timeout"
  --- 21,29 ----
    <OL>
    
    	<LI>users have reported problems with many connections stuck in the
  ! FIN_WAIT_2 state due to server timeouts. This is a quite complicated 
  ! problem; see our <A HREF="fin_wait_2.html">FIN_WAIT_2</A> page for
  ! details.
    
    	<LI>hard_timeout() for request reads uses incorrect logic, and
    ends up waiting for an initial request read for the default "timeout"
  
  
  
  1.4       +2 -3      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.3
  retrieving revision 1.4
  diff -C3 -r1.3 -r1.4
  *** perf-bsd44.html	1996/12/24 21:07:08	1.3
  --- perf-bsd44.html	1997/01/28 04:23:08	1.4
  ***************
  *** 126,134 ****
    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>
    
  --- 126,133 ----
    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.  For more details see the 
  ! <A HREF="fin_wait_2.html">FIN_WAIT_2</A> page. 
    
    <p>
    
  
  
  

Mime
View raw message