Page 1 of 1

"Freeing read locks for locker"

PostPosted: Feb 20th, '13, 23:59
by laidlaws
During updates from the command line, I see:
Code: Select all
BDB2053 Freeing read locks for locker


After looking around the Web, this has happened before (what hasn't) but on a different distro. It seemed to be related to the equivalent of the RPM database, so I rebuilt my database. The problem is still there.

Any clues, please?

Re: "Freeing read locks for locker"

PostPosted: Feb 21st, '13, 10:38
by doktor5000
Well, where is the problem related to that message?

Re: "Freeing read locks for locker"

PostPosted: Feb 25th, '13, 01:57
by laidlaws
Sorry, I wasn't specific enough.

There is no problem in that everything still works. But I haven't seen it before. Trying to update dtacut just now, it printed out about 20 times, each wirth a diffreent "locker" which seems to be a memory address, for example
Code: Select all
 BDB2053 Freeing read locks for locker 0x4fb: 3474/3074127552

The second part of the 3474 number changes half-way through the series.

Re: "Freeing read locks for locker"

PostPosted: Feb 25th, '13, 21:13
by doktor5000
If there are no related problems to rpm DB, then take that just as informational babble.
Found someone already mentioning that on Mageia: http://comments.gmane.org/gmane.linux.m ... evel/22620

Should this rehappen with any of the coming betas or RC, then i'd report that, that those messages should at least be suppressed.
What you could try is to do an rpmdb rebuild, just to see if that changes anything, maybe some minor inconsistency:
http://www.cyberciti.biz/tips/rebuildin ... abase.html