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
Date Tue, 28 Jan 1997 08:44:47 GMT
marc        97/01/28 00:44:46

  Modified:    htdocs/manual/misc  fin_wait_2.html
  Log:
  Modify the FIN_WAIT_2 docs page to change the info on Solaris (based on
  information from Mukesh Kacker <mukesh.kacker@eng.sun.com>)
  and add info on HP-UX (based on information from
  Rick Jones <raj@cup.hp.com>).
  
  Revision  Changes    Path
  1.2       +15 -2     apache/htdocs/manual/misc/fin_wait_2.html
  
  Index: fin_wait_2.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/misc/fin_wait_2.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -C3 -r1.1 -r1.2
  *** fin_wait_2.html	1997/01/28 04:23:07	1.1
  --- fin_wait_2.html	1997/01/28 08:44:45	1.2
  ***************
  *** 123,135 ****
    	    <A HREF="ftp://ftp.bsdi.com/bsdi/patches/patches-2.1/K210-027">
    	    K210-027</A> patch installed.  
    	<LI><A HREF="http://www.sun.com/">Solaris</A> as of around version
  ! 	    2.2.  The timeout may need tuning by using <CODE>ndd</CODE> to 
  ! 	    modify <CODE>tcp_fin_wait_2_flush_interval</CODE>.
    	<LI><A HREF="http://www.sco.com/">SCO TCP/IP Release 1.2.1</A>
    	    can be modified to have a timeout by following
    	    <A HREF="http://www.sco.com/cgi-bin/waisgate?WAISdocID=2242622956+0+0+0&WAISaction=retrieve">
SCO's instructions</A>.
    	<LI><A HREF="http://www.linux.org/">Linux</A> 2.0.x and
    	    earlier(?)
    </UL>
    <P>
    The following systems are known to not have at timeout:
  --- 123,148 ----
    	    <A HREF="ftp://ftp.bsdi.com/bsdi/patches/patches-2.1/K210-027">
    	    K210-027</A> patch installed.  
    	<LI><A HREF="http://www.sun.com/">Solaris</A> as of around version
  ! 	    2.2.  The timeout can be tuned by using <CODE>ndd</CODE> to 
  ! 	    modify <CODE>tcp_fin_wait_2_flush_interval</CODE>, but the
  ! 	    default should be appropriate for most servers and improper 
  ! 	    tuning can have negative impacts.
    	<LI><A HREF="http://www.sco.com/">SCO TCP/IP Release 1.2.1</A>
    	    can be modified to have a timeout by following
    	    <A HREF="http://www.sco.com/cgi-bin/waisgate?WAISdocID=2242622956+0+0+0&WAISaction=retrieve">
SCO's instructions</A>.
    	<LI><A HREF="http://www.linux.org/">Linux</A> 2.0.x and
    	    earlier(?)
  + 	<LI><A HREF="http://www.hp.com/">HP-UX</A> 10.x defaults to 
  +  	    terminating connections in the FIN_WAIT_2 state after the 
  + 	    normal keepalive timeouts.  This does not
  + 	    refer to the persistent connection or HTTP keepalive
  + 	    timeouts, but the <CODE>SO_LINGER</CODE> socket option 
  + 	    which is enabled by Apache.  This parameter can be adjusted 
  + 	    by using <CODE>nettune</CODE> to modify parameters such as
  + 	    <CODE>tcp_keepstart</CODE> and <CODE>tcp_keepstop</CODE>.
  + 	    In later revisions, there is an explicit timer for
  + 	    connections in FIN_WAIT_2 that can be modified; contact HP
  + 	    support for details.
    </UL>
    <P>
    The following systems are known to not have at timeout:
  
  
  

Mime
View raw message