Benjamin Franz wrote:
On 07/12/2010 04:58 AM, Toralf Lund wrote:
So, it seems like I managed to correctly update the repodata and all, but originally, yum concluded that it didn't need to download a new version, but could use the one cached earlier. instead.
Does anyone have any idea why this happened? How exactly does yum decide when to download new headers and when to reuse cached data?
You probably want the /etc/yum.conf file. There should be a line in it right now that reads 'metadata_expire=1h'.
Ah. Never noticed this setting before... So only the download time of the data matters, and not the server-side update time? It nearly makes sense then, although the original install was done more than 1h before the update. But maybe the headers were downloaded again after that via yum-updatesd or similar?
A delay of 1h from the repository update to the client can upgrade may not actually be a problem, as long as we know about it...
Thanks,
- Toralf
This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.