On 4/10/07, Dan McGee <dpmcgee@gmail.com> wrote:
Does my comment on this not being a bug still stand? I guess I would almost categorize this as a feature request (not to paint a bikeshed here) to have pacman hold a lock (file descriptor) on all files from the get-go so this situation can never happen. The chances of it happening are pretty rare to begin with.
Mmmh... I'm not sure if this is a bug or not, I'll let you guys decide. Anyway, I managed to debug it. Kids, don't do this at home, it killed my machine once, and only cpulimit saved me the second time :) The operation on which pacman locks is the following: debug: removing DB testing, 5 remaining... debug: returning error 22 from alpm_db_unregister : transaction already initialized This gets repeated ad infinitum, and I didn't manage to save the previous lines since even with a 1% cpu limit my 100.000 lines backlog scrolls too fast. Damn, guys, you should write slower code for pacman ;-) bardo