Bug 113773

Summary: up2date doesn't stop on ^C
Product: Red Hat Enterprise Linux 4 Reporter: Erich Morisse <emorisse>
Component: up2dateAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED WONTFIX QA Contact: Ken Reilly <kreilly>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: tsanders
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 16:04:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Sample execution and failure to close none

Description Erich Morisse 2004-01-17 17:46:23 UTC
Description of problem:
command line up2date does not stop if killed in the middle of a
download.  See attachment.

Linux emorisse.laptop 2.4.21-4.0.2.EL #1 Thu Dec 18 19:26:43 EST 2003
i686 i686 i386 GNU/Linux


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

How reproducible:
Always

Steps to Reproduce:
1.  up2date -u
2.  ^C during download of kernel (only example tried)
3.  
    

Additional info:

Comment 1 Erich Morisse 2004-01-17 17:47:13 UTC
Created attachment 97074 [details]
Sample execution and failure to close

Comment 2 Ryan Bloom 2004-05-06 18:25:58 UTC
This has been fixed in both HEAD and ERRATA_RHEL3_U1.  AS2.1 doesn't
seem to suffer from this problem.

To test this, run up2date on a package that takes a while to download,
and ctrl-c during the download phase.

Comment 4 Jiri Pallich 2012-06-20 16:04:57 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.