Bug 508534 - yum takes a big amount of time to exit while downloading
Summary: yum takes a big amount of time to exit while downloading
Keywords:
Status: CLOSED DUPLICATE of bug 524456
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-28 13:05 UTC by Cosimo Cecchi
Modified: 2014-01-21 23:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-13 15:40:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Cosimo Cecchi 2009-06-28 13:05:54 UTC 
- I was doing a yum upgrade, on a slow connection, and wanted to kill yum to save some bandwidth for browsing
- hit Ctrl+C, a message pops up saying to press Ctrl+C again to kill yum
- no matter how hard I try to press Ctrl+C, yum isn't killed, but ^C is recognized and printed on screen
- after some time (about a minute) finally yum quits
- I expected it to quit immediately after the second time I pressed Ctrl+C



(9/91): eclipse-cdt-5.0.2-3.fc11.i586.rpm                                                                                             |  15 MB     10:56 ... 

 Current download cancelled, interrupt (ctrl-c) again within two seconds to exit.

^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C

Exiting on user cancel
^C

Exiting on user cancel.
[cosimoc@pluto: ~]$
Comment 1 Mads Kiilerich 2009-09-01 19:11:43 UTC 
If this wasn't Fedora 11 it would have looked like a duplicate of bug 519233.

FWIW: My experience is that ctrl-c always worked acceptable in Fedora 11.
Comment 2 seth vidal 2009-09-01 19:24:49 UTC 
the delay in exiting, in the past has always been a dns lookup issue in python. We're waiting for a response we can't break out of b/c of how low of a level it is.
Comment 3 seth vidal 2009-10-13 15:40:48 UTC 

*** This bug has been marked as a duplicate of bug 524456 ***
Note You need to log in before you can comment on or make changes to this bug.