diff options
author | 2012-10-01 23:01:29 -0400 | |
---|---|---|
committer | 2012-10-01 23:01:29 -0400 | |
commit | 3dfe4819b992b5486f5bca5fda9f64c7b3ed24a6 (patch) | |
tree | 498640c261666014080b9f129aab6286d6527171 /doc/bugs/signal_weirdness.mdwn | |
parent | 7701976d6d40697ef40701c0b4c38321e6ca2ceb (diff) |
bring back default SIGINT handler
This seems to fix a problem I've recently seen where ctrl-c during rsync
leads to `git annex get` moving on to the next thing rather than exiting.
Seems likely that started happening with the switch to System.Process
(d1da9cf221aeea5c7ac8a313a18b559791a04f12), as the old code took care
to install a default SIGINT handler.
Note that since the bug was only occurring sometimes, I am not 100% sure
I've squashed it, although I seem to have.
Diffstat (limited to 'doc/bugs/signal_weirdness.mdwn')
-rw-r--r-- | doc/bugs/signal_weirdness.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs/signal_weirdness.mdwn b/doc/bugs/signal_weirdness.mdwn index a7cc14642..1942a924a 100644 --- a/doc/bugs/signal_weirdness.mdwn +++ b/doc/bugs/signal_weirdness.mdwn @@ -14,7 +14,7 @@ For example: Here git-annex exits before rsync has fully exited. Not a large problem but sorta weird. -The culprit is `safeSystemEnv` in Utility.SafeCommand, which installs +The culprit is `CmdLine.startup` in Utility.SafeCommand, which installs a default signal handler for SIGINT, which causes it to immediatly terminate git-annex. rsync, in turn, has its own SIGINT handler, which prints the message, typically later. |