[SERVER-305] ctrl-c in shell should terminate currenct command Created: 22/Sep/09 Updated: 12/Jul/16 Resolved: 22/Feb/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.3 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Dwight Merriman | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Comments |
| Comment by auto [ 22/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: Revert "Revert " This reverts commit 149248b4eb1a8f0cbfe28c4d43c4d2664b00b063. |
| Comment by auto [ 22/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: Revert " This reverts commit ae80a66ff8d30bc9785d12a5f9d8fafd0bc37e2a. |
| Comment by auto [ 22/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 22/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Aaron Staple [ 18/Feb/10 ] |
|
I should record the uri on connect, not on scope creation |
| Comment by auto [ 18/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 17/Feb/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Dwight Merriman [ 26/Jan/10 ] |
|
this can be deferred for any time in the near future as i think the right way to do now would be killOp, and that is complicated we should make sure if the shell is printing a very large set of output, that is interruptible by ctrl-c, which may already be true not sure. |
| Comment by Eliot Horowitz (Inactive) [ 26/Jan/10 ] |
|
No - it should use the same mechanism as killOp() |
| Comment by Aaron Staple [ 26/Jan/10 ] |
|
I'm assuming this is only supposed to work for operations that have yield implemented (update & delete according to another jira). Is that correct? If the update/delete is being called indirectly via a command, I think we shouldn't allow interruption to avoid inconsistent data resulting from a partially completed command. |
| Comment by Eliot Horowitz (Inactive) [ 20/Oct/09 ] |
|
this can't happen until after concurrency - so moving for now |
| Comment by Dwight Merriman [ 15/Oct/09 ] |
|
this is tricky to implement as kill current op might kill someone else's operation. |