From owner-freebsd-current Sun May 9 13: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 74B8E15864 for ; Sun, 9 May 1999 13:02:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id NAA15155; Sun, 9 May 1999 13:02:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA36037; Sun, 9 May 1999 13:02:15 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905091912.MAA06832@flamingo.McKusick.COM> Date: Sun, 09 May 1999 13:02:15 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Kirk McKusick Subject: Re: Disappearing/Reappearing Files... (fwd) Cc: current@freebsd.org, Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk McKusick wrote: > The changes that I added to soft updates two days ago only kick in > when the soft dependency memory limit is hit. This certainly should > not be happening at system startup, and on any machine with more > than 64Mb of memory, almost never. In my case it looks like your changes weren't the problem. I've had a failure without soft updates, and I'm fairly confident that it's a HW problem at this point. (I've only had the machine for a few days.) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message