On 12/05/2007 02:43:57 AM, David Timms wrote:
> Geoffrey Leach wrote:
> > I'm running yumupdated on F8 with the defaults (no download). It
> > appears to be causing a significant amount of inbound traffic
> (200MB)
> > every few days. Is this expected?
>
> It is possibly normal.
> If there are no updates in any enabled repo, then yum-upatesd should
> download:
> - the mirrorlist {usually<1kB}
> - the mirrors repomd.xml {2.3kB}
>
> The repomd contains info on the current:
> - primary.sqlite {7.7MB}
> - updateinfo.xml.gz {435.2kB}
>
> If the checksum and size of the previously downloads of those files
> match the repomd.xml, then the above two files won't be downloaded.
>
> If the checks indicate that those two files differ, then at minimum
> thost two will get downloaded. There is updates most days, hence I
> expect that those four files would get updated and downloaded.
>
> Sometimes, an additional thing can go wrong: sometimes mirrors aren't
> up
> to date. This can lead to a problem where the downloaded repomd.xml
> shows that there has been a change in updates; but each mirror that
> the
> download of the second pair of files comes from might show that a
> mismatch with the repomd, until one finally has the correct file.
> This
>
> could also apply to the packages downloaded during update.
>
> In the last week or so there has been some sizable updates eg two
> firefox {20MB+}, perl {10MB}, python {5MB}, tetex {13MB}, kdegames
> {11MB}
Thanks. The trace of IP addresses suggested that yumupdated might have
been in a loop probinv various repositories. If the mirrors were out of
sync that could have been the problem.
