From owner-freebsd-ports@FreeBSD.ORG Fri Oct 5 16:01:52 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 635DC106564A for ; Fri, 5 Oct 2012 16:01:52 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id B74088FC08 for ; Fri, 5 Oct 2012 16:01:51 +0000 (UTC) Received: (qmail 98819 invoked by uid 89); 5 Oct 2012 16:01:43 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@80.190.102.230) by mail.grem.de with ESMTPA; 5 Oct 2012 16:01:43 -0000 Date: Fri, 5 Oct 2012 18:01:43 +0200 From: Michael Gmelin To: freebsd-ports@freebsd.org Message-ID: <20121005180143.0ff657fe@bsd64.grem.de> In-Reply-To: <506F0115.5090302@shatow.net> References: <506E9927.8030001@mail.zedat.fu-berlin.de> <506EFCB8.1050907@shatow.net> <506EFF67.8060401@zedat.fu-berlin.de> <506F0115.5090302@shatow.net> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: ports-mgmt/portupgrade: ** Database file locked. Waiting. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2012 16:01:52 -0000 On Fri, 05 Oct 2012 10:47:33 -0500 Bryan Drewery wrote: > On 10/5/2012 10:40 AM, O. Hartmann wrote: > > Am 10/05/12 17:28, schrieb Bryan Drewery: > >> On 10/5/2012 3:24 AM, O. Hartmann wrote: > >>> Using pkg(ng) in conjunction with the port ports/mgmt/portupgrade > >>> results in long waiting cycles when portupgrade is updating the > >>> local database, it is even on fast boxes sometimes in the range > >>> of a minute or even two. > >> > >> You mean ports-mgmt/portupgrade-devel right? > > > > Of course, yes. > > > >> > >>> > >>> Is this usual or is there something wrong with my setup? > >>> > >>> Regards, > >>> Oliver > >>> --- > >>> > >>> [Updating the pkgdb in /var/db/pkg ... - 1114 > >>> packages found (-0 +1) . done] > >>> ---> Cleaning out obsolete shared libraries > >>> [Updating the pkgdb in /var/db/pkg ... USING > >>> PKGNG ** Database file locked. Waiting. > >> > >> I have not experienced this. Are you running multiple portupgrade > >> tools at once? > > > > No, there is only one instance running at the same time, but apart > > from the usual installations, I use Ruby 1.9 on all machines, I > > guess Ruby 1.8 is still the default. > > I am using 1.9 as well. > > > > > But anyway, the long locking time is a bit of frustrating, since it > > takes ages for updating large sets of ports (as done recently on > > FreeBSD 9.1-PRE). > > > > > Strange, I am unable to recreate this. > I've been experiencing the same issue on various machines (different versions of portupgrade and portupgrade-devel, different versions of ruby etc.) for years. Some machines seem more prone to it than others (only had the issue on machines using UFS+SU, but that might be coincidental).