On Tue, 2010-04-06 at 14:44 -0400, Seth Vidal wrote: > > On Tue, 6 Apr 2010, Adam Williamson wrote: > > > However, we already established that the problem case is when it runs > > right after you've done a yum operation, in which case the metadata has > > already just been refreshed, and it should be using the already-cached > > metadata. In that case, does it need to lock? > > If the metadata is current then the operation is really quite quick. > > If this lock is taking longer than that then it is worth knowing what's > not the same. > > -sv > The lock is longer, because PK is downloading content not normally used directly by yum (updateinfo IIRC), which makes it not read-only, which makes it require the lock. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
