From: Marc Slemko Date: Tue, 28 Jan 1997 08:44:45 +0000 (+0000) Subject: Modify the FIN_WAIT_2 docs page to change the info on Solaris (based on X-Git-Tag: APACHE_1_2b7~22 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=960c197d2ec524206743158db153cf1dde538c97;p=apache Modify the FIN_WAIT_2 docs page to change the info on Solaris (based on information from Mukesh Kacker ) and add info on HP-UX (based on information from Rick Jones ). git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77525 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/fin_wait_2.html b/docs/manual/misc/fin_wait_2.html index d4aa20e478..fe65c7c790 100644 --- a/docs/manual/misc/fin_wait_2.html +++ b/docs/manual/misc/fin_wait_2.html @@ -123,13 +123,26 @@ The following systems are known to have a timeout: K210-027 patch installed.
  • Solaris as of around version - 2.2. The timeout may need tuning by using ndd to - modify tcp_fin_wait_2_flush_interval. + 2.2. The timeout can be tuned by using ndd to + modify tcp_fin_wait_2_flush_interval, but the + default should be appropriate for most servers and improper + tuning can have negative impacts.
  • SCO TCP/IP Release 1.2.1 can be modified to have a timeout by following SCO's instructions.
  • Linux 2.0.x and earlier(?) +
  • HP-UX 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 SO_LINGER socket option + which is enabled by Apache. This parameter can be adjusted + by using nettune to modify parameters such as + tcp_keepstart and tcp_keepstop. + In later revisions, there is an explicit timer for + connections in FIN_WAIT_2 that can be modified; contact HP + support for details.

    The following systems are known to not have at timeout: