-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ctrl-c did not always terminate the vagrant running process #532
Comments
Root cause: Mintty was failed when running as background process! It will ignore SIGNALS( SIGINT, SIGKILL, SIGTERM ). I still have no way to solve this problem! I need to discuss to resolve the problem. |
The problem is that the mintty is not fully compatible with the window. Should use
****** TESTED ******* |
so we need to use git-bash instead of cygwin |
assigned to @phuonglm to check and confirm on this. If this bug only happens on Cygwin, not Git-Bash, then Git-Bash is preferred to use and we'll deprecate Cygwin when Git-Bash is proven to be stable and better than Cygwin. |
@hieptranquoc said that it looked like the problem is fixed on the recent latest version of cygwin, need @phuonglm to verify on this. If so, we don't need to use the wrapper anymore. |
@hieptranquoc, I clean install windows 7 x64 cygwin and vagrant 2.2.4, virtualbox 6.0.8 but still got the problem with ctrl+c, could you specify more details about your version |
I ran with window 10 - x64. If windows 7 and windows 8 can not use |
assign to @hoavt to verify the current (workaround) solution. |
ctrl-c did not always terminate the vagrant running process #532 - fi…
assigned to @phuonglm to verify and confirm. |
Verified on windows 7 and windows 10 x64 when used |
closed, thank you. |
and it causes errors, especially on Windows - Cygwin, for example, running some vagrant commands did not work). We need to investigate the root cause.
related:
vagrant powershell
hashicorp/vagrant#8903The text was updated successfully, but these errors were encountered: