ports-mgmt/portupgrade: ** Database file locked. Waiting.
Bryan Drewery
bryan at shatow.net
Fri Oct 5 15:47:31 UTC 2012
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.
# pkgdb -fu
---> Updating the pkgdb
[Rebuilding the pkgdb <format:bdb_btree> in /var/db/pkg ... USING PKGNG
- 433 packages found (-0 +433)
....................................................................................................100....................................................................................................200....................................................................................................300....................................................................................................400.................................
done]
Do you have some package tool in crontab perhaps?
The PKGNG implementation in portupgrade is far from ideal. It will
require a major refactoring of portupgrade to make it more efficient.
Just focusing on making it *work* now, and will speed it up later.
>>
>> Bryan
>>
>
>
More information about the freebsd-ports
mailing list