[SERVER-7608] Mongo Shell cannot be interrupted without a SIGKILL Created: 09/Nov/12 Updated: 07/Apr/23 Resolved: 04/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Eric Sabban | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 1 |
| Labels: | shell | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux, OSX |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
When mongo shell encounters a command, say db.printSlaveReplicationInfo() that doesn't come back, CTRL-C, CTRL-Z, or CTRL-\ are unresponsive. This is very annoying because I have to close my shell/exit my terminal. CTRL-C should stop the operation, or at least kill the connection and reconnect. CTRL-\ should crash the process, dropping me into my main shell, and CTRL-Z should background. Please stop catching these events, it's REALLY annoying. |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Sep/14 ] |
|
I'm no longer to reproduce this behavior in more recent versions of MongoDB like 2.4.11 and 2.6.4. I used the bug reported on fumduq, I'm going to mark this issue as resolved, but if you're still able to reproduce this behavior in a more recent version please feel free to reopen the ticket and provide reproduction steps. Regards, |