Date: Fri, 5 Oct 2012 18:01:43 +0200 From: Michael Gmelin <freebsd@grem.de> To: freebsd-ports@freebsd.org Subject: Re: ports-mgmt/portupgrade: ** Database file locked. Waiting. 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 05 Oct 2012 10:47:33 -0500 Bryan Drewery <bryan@shatow.net> 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 <format:bdb_btree> in /var/db/pkg ... - 1114 > >>> packages found (-0 +1) . done] > >>> ---> Cleaning out obsolete shared libraries > >>> [Updating the pkgdb <format:bdb_btree> 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).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121005180143.0ff657fe>