Re: Re: Horrible response to keyboardInterrupt

On Thu, 2008-09-11 at 21:17 -0700, CAI Qian wrote:

> I think it is of yum users' interests when making language decision.

making a language decision? whatever.

> There is another example of bad usability for handling CTRL-C,
> 
> [root@localhost ~]# yum -d 10 update
> Config time: 0.107
> Yum Version: 3.2.19
> COMMAND: yum -d 10 update 
> Installroot: /
> Reading Local RPMDB
> rpmdb time: 0.001
> Setting up Package Sacks
> pkgsack time: 0.003
> Setting up Update Process
> Building updates object
> ^C^C^C^C^C^C^C^C^C^C^C^C^C^C^Cup:Obs Init time: 0.733
> ^C^Cputting kpathsea in complex update
> 
> ...
> 
> You could see from the above, I have to hit CTRL-C more than 10 times
> in order to cancel the operation. Far more than tolerant for reasonable
> user experience. Is it the same thing as the Python socket handling
> bug?
> 

Actually, you don't have to hit it that many times. You are hitting it
that many times. What's happening at that particular point is that the
rpmdb is being accessed. At which point rpm is holding the signal
handler that would allow that interrupt to work.

-sv