Date: Tue, 22 Mar 2005 19:58:51 +0100 From: Robert Gogolok <robertgogolok@web.de> To: ray@redshift.com Cc: freebsd-net@freebsd.org Subject: Re: FIN_WAIT_2 Message-ID: <42406AEB.8020906@web.de> In-Reply-To: <3.0.1.32.20050322104506.00a8b8b8@pop.redshift.com> References: <3.0.1.32.20050322102130.00a7be40@pop.redshift.com> <3.0.1.32.20050322102130.00a7be40@pop.redshift.com> <3.0.1.32.20050322104506.00a8b8b8@pop.redshift.com>
next in thread | previous in thread | raw e-mail | index | archive | help
ray@redshift.com wrote: > I was actually referring to the keepalive setting in httpd.conf :-) But yes, > you can change the sysctl setting also. I believe that will have a positive > impact on the server. I don't have any first hand experience with it however. > > What do you have in httpd.conf ? KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 15 The strange thing (for me) is: tcpdump output: tcp4 0 0 HTTP_SERVER.80 81.56.174.131.34347 FIN_WAIT_2 The last access from this client was today 22/Mar/2005:11:19:39 according to the http-access file. It's 19:56 at the moment. So over 6 hours in FIN_WAIT_2 state, is that normal? Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42406AEB.8020906>