Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 05 Oct 1998 16:32:33 -0700
From:      David Greenman <dg@root.com>
To:        Christopher Nielsen <enkhyl@hayseed.net>
Cc:        "Mikhail A. Sokolov" <mishania@demos.net>, current@FreeBSD.ORG
Subject:   Re: -current panics.. 
Message-ID:  <199810052332.QAA16333@implode.root.com>
In-Reply-To: Your message of "Mon, 05 Oct 1998 14:32:56 PDT." <Pine.LNX.4.04.9810051426560.13926-100000@hillbilly.hayseed.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
>>    Properly tuned, FreeBSD will work just fine for large servers. You have to
>> know what you are doing, however. This will be the case for ALL operating
>> systems, not just FreeBSD. I'm not convinced that there are any "leaks" in
>> FreeBSD. All of those that I have investigated have turned out to be just
>> a large average number of TIME_WAIT connections that haven't timed out yet.
>> The system must be configured with this in mind or you will run out of
>> buffers.
>
>This same kind of situation can occur with a network-intensive app running
>under Solaris, too. From my own experience with tuning OSs (specifically
>Solaris 2.x), I'd agree with David's assessment. Not having delved that
>far into the details of FreeBSD "leaks" as he probably has, I can't say
>with certainty that there are none, but I'm inclined to believe him. :-)

   I should say here that I'm not saying that there aren't any "leak" bugs,
either, just that I have looked into this several time and found nothing but
mis-tuned systems. I'm also a bit incredulous since wcarchive does far more
TCP/IP than most other machines in the world, has months of uptime and no
detectable buffer leaks. I want to be clear about this: If there was a bug
that I could identify, I'd fix it immediately. "Show me the mon^H^H^Hbug!"

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810052332.QAA16333>