On Sat, 2008-10-04 at 19:24 -0500, Matt Domsch wrote: > MM indexes the master mirror file system every 4-6 hours, so it > shouldn't be out of date longer than this.
Interesting, what does this mean? Can we do something more often that just checks for new repomd.xml files and does the checksums? Also given the message on the infrastructure list, could that be related? -- Although I only saw it for about 6-8 hours (I think I saw the first problems around 16:00, not 100% on that though. Everything seems to be fine now. > I need to implement a > better way to know when directories change and index those that change > more frequently more often. Regardless, any index updates don't > propogate to the mirrorlist cache until the top of the hour, so there > will always be that much of a delay... *nods* ... do we know when rel-eng push new updates¹ and/or when mirrors run rsync? My guess is even a constant 60 minutes won't be too bad, but 6 hours could be annoying. Also while it won't help us right now, is it possible to get MM to obey/use "Accept-Encoding: gzip"? ¹ The rawhide repomd.xml files have a timestamp of 5:50-6:20, I'd guess they get pushed just after that? -- James Antill <[EMAIL PROTECTED]> Fedora _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
