From owner-freebsd-stable Mon Sep 27 10:31: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 495AA15427 for ; Mon, 27 Sep 1999 10:30:55 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 11Vebt-00029a-00; Mon, 27 Sep 1999 10:30:45 -0700 Date: Mon, 27 Sep 1999 10:30:44 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Mikhail Teterin Cc: stable@freebsd.org Subject: Re: nmap V. 2.3BETA5 causes panic In-Reply-To: <199909271718.NAA40833@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Sep 1999, Mikhail Teterin wrote: > be so tactless to point it out, but it is FreeBSD-2.2*. Once, after 3 > monthes of uptime, I tried to simulate an "attack" on my (colocated) > web-server -- a humble P100 with 32Mb of RAM on 100Mb network -- by > issuing numerous fetch-requests from a machine nearby. The requests > where steadily growing in number and in a couple of minutes the server > locked up. I was preparing to call the ISP (Ziplink) to ask them to > reboot it, but it unlocked in about 40 seconds. There were "out of mbuf" > messages in the log, but it stayed up for over 10 more monthes (!) until > finaly its IDE disk started to glitch. Yes, 2.2-stable does recover from mbuf shortages better than 3.2-stable. Howerver, be aware that the GENERIC kernel does not have enough mbufs by default to run a serious server. Setting MAXUSERS to 64 gives you quite a number of additional mbufs. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message