Description of problem:
Currently, up2date pipes all updates off of Redhat's servers. During
peak load times, this results in unacceptably long transmission
times-- frequently so long that up2date simply fails, but without
giving any message to that effect to the user.
Suggestion: instead of using the current ftp/http-like model, move it
to a swarming model such as BitTorrent. Using a swarming model, the
load on RH's servers would vary from (at best case) having to serve up
nothing more than the MD5 keys; to at worst having to serve up a
single copy of the file in question. The reduction in required
resources at RH looks pretty enormous from this perspective, as does
the improvement in distribution of updates.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous comment. If this still occurs on FC3
or FC4 and is a security issue, please assign to Fedora Legacy and the
appropriate version. The bug could also be filed against RHEL if it is relevant
up2date has been replaced by pirut and pup in FC5 and FC6, the still fully
supported versions of Fedora Core, so this bug will not be fixed unless it is a