Skip to content

Conversation

@kellyfelkins
Copy link

Previously it was often difficult to kill a rails server if rinruby had run. Rinruby would trap INT and do nothing, effectively preventing a user from canceling a running server.

The concept of these changes is to reset the trap to its original state after the trap established by rinruby is no longer needed. I'm not sure this is correct.

Thank you.

fenrir-naru added a commit to fenrir-naru/rinruby that referenced this pull request Aug 28, 2018
* clbustos#17 is included (restoring original INT handler)
fenrir-naru added a commit to fenrir-naru/rinruby that referenced this pull request Aug 29, 2018
* clbustos#17 is included (restoring original INT handler)
* TODO: I18N (multi-byte string)
fenrir-naru added a commit to fenrir-naru/rinruby that referenced this pull request Aug 29, 2018
* clbustos#17 is included (restoring original INT handler)
* TODO: I18N (multi-byte string)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant