Geoffrey Leach <geoff@xxxxxxxxxx> wrote: >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. This isn't the first time we've had reports of yumupdatesd misbehaving in the face of problems with mirrors: https://bugzilla.redhat.com/show_bug.cgi?id=374801 That bug has been closed as fixed, even though the only fix was to repair the broken file on the mirrors. That doesn't address the underlying issue that yumupdatesd should be better behaved when things go wrong. Because things /will/ go wrong. For people with limited bandwidth, or capped bandwidth, or who pay by quantity of data transferred it's unaccpetable that yumupdatesd should sit in a loop downloading broken files from mirrors. That's what needs to be fixed. Ron
