> You're probably opened the cache without holding a lock, and > an update ran in parallel. That's really the only possible > explanation I could think of.
Is there a way to hold a lock as a normal user process? (oneconf is an user session service) If not is there a standard way to detect that something is changing the cache under your feet and to deal with that? Cheers, Sebastien Bacher
