From owner-freebsd-current Tue Feb 16 06:28:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23573 for freebsd-current-outgoing; Tue, 16 Feb 1999 06:28:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23555 for ; Tue, 16 Feb 1999 06:28:41 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA58217; Tue, 16 Feb 1999 09:28:32 -0500 (EST) Date: Tue, 16 Feb 1999 09:28:32 -0500 (EST) From: John Fieber To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: Problems in VM structure ? In-Reply-To: <199902160819.AAA22168@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Feb 1999, Matthew Dillon wrote: > Try reducing maxusers to 128. Another person reported similar behavior > to me and after a bunch of work he tried going back to a basic > distribution -- and everything started working again. > > It turned out that a maxusers value of 256 and 512 were causing his machine > to go poof, but a maxusers value of 128 worked fine. Another datapoint, Sybase goes poof with maxusers set to 64 or higher. This has been the case since before 3.0 was released. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message