Date: Thu, 29 May 2008 09:02:52 -0400 From: Robert Blayzor <rblayzor.bulk@inoc.net> To: sclark46@earthlink.net Cc: freebsd-stable@freebsd.org Subject: Re: Sockets stuck in FIN_WAIT_1 Message-ID: <96AFE8D3-7EAC-4A4A-8EFF-35A5DCEC6426@inoc.net> In-Reply-To: <483EA513.4070409@earthlink.net> References: <B42F9BDF-1E00-45FF-BD88-5A07B5B553DC@inoc.net> <1A19ABA2-61CD-4D92-A08D-5D9650D69768@mac.com> <23C02C8B-281A-4ABD-8144-3E25E36EDAB4@inoc.net> <483DE2E0.90003@FreeBSD.org> <B775700E-7494-42C1-A9B2-A600CE176ACB@inoc.net> <483E36CE.3060400@FreeBSD.org> <483E3C26.3060103@paradise.net.nz> <483E4657.9060906@FreeBSD.org> <483EA513.4070409@earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 29, 2008, at 8:44 AM, Stephen Clark wrote: > You know it really pains me when people blithely say just upgrade to > X.X where X is the latest release. > > It is generally just not that simple to upgrade - there are all > sorts of dependencies with other software that have to be considered. I don't mind upgrading this box, it does need it, and it's just a web server. But I see your point. What bothers me is that suggesting an upgrade "may" fix the problem. I really want to know that upgrading WILL fix the problem. I know it might not hurt, but if it doesn't address the primary issue at hand, I can spend time and resources trying to figure out why. Regardless since this is just a mirror web server, I'm going to run it on box using 7.0 and see what I get. I realize a lot of network code has changed from 4.x to 6.x (and maybe 7.x) so I'm going to give that a go. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net http://www.inoc.net/~rblayzor/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96AFE8D3-7EAC-4A4A-8EFF-35A5DCEC6426>