From owner-freebsd-current  Tue Feb 16 00:19:27 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA20940
          for freebsd-current-outgoing; Tue, 16 Feb 1999 00:19:27 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20935
          for <current@FreeBSD.ORG>; Tue, 16 Feb 1999 00:19:25 -0800 (PST)
          (envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id AAA22168;
	Tue, 16 Feb 1999 00:19:07 -0800 (PST)
	(envelope-from dillon)
Date: Tue, 16 Feb 1999 00:19:07 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199902160819.AAA22168@apollo.backplane.com>
To: Khetan Gajjar <khetan@chain.freebsd.os.org.za>
Cc: current@FreeBSD.ORG
Subject: Re: Problems in VM structure ?
References:  <Pine.BSF.4.05.9902152325310.518-100000@chain.freebsd.os.org.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:maxusers	256

    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.

    I haven't tracked the problem down yet.  Please try reducing your maxusers
    to 128 and email the results to current.

						    -Matt


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