[darcs-devel] [issue465] darcs takes ages to respond to control-C
in some states
Isaac Dupree
bugs at darcs.net
Wed May 23 07:58:25 PDT 2007
New submission from Isaac Dupree <isaacdupree at charter.net>:
E.g. in a GHC repo:
$ darcs pull
[type control-C soon but not immediately]
[wait a while - around 15 seconds in my case]
withSignalsHandled: Interrupted!
$
After typing ^C the system appears to have high network (not CPU) usage
for some time before quitting.
Waiting a long time, unresponsively, before quitting when requested, is
not nice behavior for a unix process :)
(also "withSignalsHandled: Interrupted!" seems odd to say;
"withSignalsHandled" is part of the implementation. "Interrupted by
signal X" or some such might be better?)
Isaac
----------
messages: 1704
nosy: EricKow, beschmi, droundy, isaacdupree, tommy
status: unread
title: darcs takes ages to respond to control-C in some states
____________________________________
Darcs issue tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue465>
____________________________________
More information about the darcs-devel
mailing list