From owner-freebsd-current Thu Jun 27 7:40:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 1033437B401; Thu, 27 Jun 2002 07:40:42 -0700 (PDT) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17NaSm-000DGp-00; Thu, 27 Jun 2002 16:41:36 +0200 Date: Thu, 27 Jun 2002 16:41:36 +0200 From: Sheldon Hearn To: Dag-Erling Smorgrav Cc: current@freebsd.org Subject: Re: i386 tinderbox failure Message-ID: <20020627144136.GH18764@starjuice.net> Mail-Followup-To: Dag-Erling Smorgrav , current@freebsd.org References: <200206270200.g5R20Aix005253@ref5.freebsd.org> <20020627143336.GG18764@starjuice.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020627143336.GG18764@starjuice.net> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On (2002/06/27 16:33), Sheldon Hearn wrote: > I got this testing the RMEM_LIMIT patches, but it only crops up after > about an hour of heavy ports building. You'll get this for just any > binary that uses mmap(). > > Unfortunately, I haven't had time to produce any useful debugging > information, so I can't be sure it's really the RMEM_LIMIT patches. FUD. :-( Tor Egge found the feal problem, which had nothing to do with the RLIMIT_VMEM stuff. Sorry, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message