Very early SIGINTs no longer cause ugly stack traces.

We catch INT very very early in the Vagrant process in order to exit
cleanly rather than raising any exceptions. This is eventually overriden
by Vagrant at some point.
This commit is contained in:
Mitchell Hashimoto 2012-08-10 00:30:58 -07:00
parent 42744f71e8
commit de73b65635
2 changed files with 8 additions and 0 deletions

View File

@ -40,6 +40,8 @@
keystrokes such as ctrl-D and ctrl-C are more gracefully handled. [GH-1017]
- Fixed bug where port check would use "localhost" on systems where
"localhost" is not available. [GH-1057]
- Sending a SIGINT (Ctrl-C) very early on when executing `vagrant` no
longer results in an ugly stack trace.
## 1.0.3 (May 1, 2012)

View File

@ -1,4 +1,10 @@
#!/usr/bin/env ruby
# Trap interrupts to quit cleanly. This will be overriden at some point
# by Vagrant. This is made to catch any interrupts while Vagrant is
# initializing which have historically resulted in stack traces.
Signal.trap("INT") { exit 1 }
require 'log4r'
require 'vagrant'
require 'vagrant/cli'