On Thu, 2008-02-21 at 10:45 -0500, James Antill wrote: > How does this work? > > instance 1: > > lock repo X. > get repomd.xml and new primary > unlock repo X. > > instance 2: > > lock repo X. > get repomd.xml and new primary > get filelists > unlock repo X. > > instance 1: > > lock repo X. > get filelists > > ...there is no guarantee that instance 2 didn't change the > repomd/primary/etc.
There isn't a guarantee, there is a higher-than-likely change it will not b/c instance1 just a got a new 1. The metadata caching means instance2 will likely just see that and skip it. The point isn't bad but I bet if we implemented the above we'd see only an occasional locking complaint. -sv _______________________________________________ Yum-devel mailing list Yum-devel@linux.duke.edu https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
