[Yum-devel] [UG] ctrl-c not doing what is expected

[Gijs Hollestelle]

On 4/16/05, seth vidal <skvidal at phy.duke.edu> wrote:
> Hey guys,
>  Have we ever gotten to the bottom of the ctrl-c skips-to-next-mirror
> instead of exiting, problem? I'm asking b/c if there's a way to make it
> just exit like folks expect I'd be in favor of it, I think.

I agree it should just exit, but I don't think this will be easy to
fix because there is no way to distinguish between the user pressing
ctrl-c and a network error. In both cases python throws a a
socket.error which grabber.py catches.

Greets,
  Gijs