[Yum-devel] RFC: Make keyboard interupt timeout bigger

James Antill james.antill at redhat.com
Wed Nov 21 04:30:41 UTC 2007


 So we've been getting a few BZ/comments in Fedora on and off about how
it's "hard" to C-c yum, even after the rpm/yum fix. The currently open
one being:

https://bugzilla.redhat.com/show_bug.cgi?id=358391

...I think I've found the "problem" and an obvious solution, currently
yum uses a 0.2 second timeout and at least in certain situations that
isn't enough. With a manual change to make this say a 5 second timeout
it is still very unlikely to be done by accident and should cover any
sane latency edge cases.
 Of course testing this isn't easy, for instance running multiple python
-c 'while True: pass' and/or dd if=/dev/zero of=/tmp/abcd didn't seem to
trigger the problem for me (Ie. I could still exit with a 0.2 second
timeout). So I'm going mostly from the data I captured in one case where
it wasn't working and I had debug data (comment #14 in above BZ), and I
just took the longest latency there and doubled it to get 5 seconds.

 Anyone have any violent reactions to upping the timeout?
 Anyone want a bigger/smaller timeout than 5 seconds?

-- 
James Antill <james.antill at redhat.com>
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.baseurl.org/pipermail/yum-devel/attachments/20071120/5c7fe365/attachment.pgp 


More information about the Yum-devel mailing list