Les Mikesell wrote: [snip] >>> I run several machines >>> through the same caching http proxy and when I first started it seemed >>> like most files would be cached. Now, with no change at my end it >>> seems like there is never a cache hit even when another machine just >>> performed the same update. Is there a way to force the order of mirror >>> attempts to be the same so the cache will work again? >> >> Remove the mirror list and set yum to use the mirror you prefer. >> > > If they are identical, how would I determine a preference? Or if they > aren't identical, how would I know? Huh? What are "they" in this context? >> Or set >> up a local yum repo and point them all to that. > > That would mean (a) knowing all the versions that need to pull updates > and (b) copying a lot of stuff in the repo that nobody has installed which > seems a lot worse than letting a cache do its job. Depends on the situation. A local yum repo gives you greater control in what updates are applied and win. I just presented it as another option. > Wouldn't this be better-handled by round-robin DNS, assuming that > the target hosts are not configured as name-based virtual hosts or that > they have the appropriate configuration to respond to the same name? Not all mirrors have the same directory layout. Also, since the mirrors are community run, it is impossible to know if they are virtual hosts or not. -- William Hooper
