From owner-freebsd-stable Tue Aug 11 13:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26660 for freebsd-stable-outgoing; Tue, 11 Aug 1998 13:09:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA26647; Tue, 11 Aug 1998 13:09:35 -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 0z6Khu-0006Ft-00; Tue, 11 Aug 1998 13:07:46 -0700 Date: Tue, 11 Aug 1998 13:07:44 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Stefan Bethke cc: Thomas Gellekum , "Jordan K. Hubbard" , freebsd-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: <1682190.3111854089@d254.promo.de> 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 Tue, 11 Aug 1998, Stefan Bethke wrote: ... > As a relief you can try to increase the number of mbufs; however, this will > only make the case less likely to occur. ... Actually, if you limit the number of processes per user, you can almost completely prevent it from happening (at least for regular users anyhow). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message