Bug 87519 - up2date does not allow pause or resume.
up2date does not allow pause or resume.
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Adrian Likins
Red Hat Satellite QA List
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-03-27 23:12 EST by Adam Greenberg
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-02 15:06:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Greenberg 2003-03-27 23:12:28 EST
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible: not applicable

Steps to Reproduce: Not applicable
Actual results:

Expected results:

Additional info:
1.  The up2date utility does not allow me to pause a download or resume one that
has failed.  The latter is a big problem.  I have only 56k access and large
downloads (kernels) frequently suffer abrupt termination by the RHN server.  I
have no recourse but to restart the entire download.  It would be enormously
usefule if up2date could checkpoint itself periodically and allw me to resume
from the last checkpoint in the event of a connection failure.

2.  When I select multiple packages for download, up2date appears to treat the
collection selected as an all or nothing download.  If any of the component
downloads fail with a connection termination, the entire download fails and
up2date terminates.  A fix for (1) above would help this probnlem too.
Comment 1 Adrian Likins 2004-09-02 15:06:09 EDT
Current versions support resume (it will start over from
where it left off on particully downloaded packages).

Pause is mentioned in other pending RFE's so closing this currentrelease.

Note You need to log in before you can comment on or make changes to this bug.