From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 09:11:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A57B16A4CE for ; Tue, 13 Jan 2004 09:11:36 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20A7943D54 for ; Tue, 13 Jan 2004 09:11:35 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 142AA72DC7; Tue, 13 Jan 2004 09:11:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 11AFD72DBF; Tue, 13 Jan 2004 09:11:35 -0800 (PST) Date: Tue, 13 Jan 2004 09:11:35 -0800 (PST) From: Doug White To: Edwin Culp In-Reply-To: <20040113160919.1900.qmail@web13006.mail.yahoo.com> Message-ID: <20040113090728.R63000@carver.gumbysoft.com> References: <20040113160919.1900.qmail@web13006.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: Tuc Subject: Re: Signal 6's with ruby apps such as portupgrade and pkg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 17:11:36 -0000 On Tue, 13 Jan 2004, Edwin Culp wrote: > > I renamed it, tried, and it didn't work. I went to > > look, and > > there was a pkgdb.db from 4 days ago there?! So I > > deleted it, and now it > > seems to work! > Tux, > > mine is now working thanks to a lot suggestions from > folks here and on the questions list that have had > similar problems. > Something else you might be tripping over is a change to the statfs system call prior to 5.2. This is particularly important if you haven't been following -current. You need to rebuild anything using statfs or you'll have wierd failures. In your case it apears to be a corrupted db but if you're having other wierd problems, try rebuilding the affected apps. > The two significant things that I've done are to link > malloc.conf to aj > > ln -s aj /etc/malloc.conf This turns off the fatal flag and the filling of memory before use. The J option in particular will improve performance. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org