-
Notifications
You must be signed in to change notification settings - Fork 181
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
In v1.3.0, cannot kill child process when using control-c in Windows #80
Comments
Setting |
Any changes with this? |
haven't heard anything... staying on 1.2.3 til otherwise |
@wlingke Do you do anything to get the stdout piped to the main proc? Using inherit breaks with the older versions. |
The stdout pipes normally to the main process for me. Not sure what you Best, Lingke Wang On Fri, Mar 13, 2015 at 8:20 AM, Matthew Robb [email protected]
|
any luck on this issue? This still persists in the latest forever monitor |
good job on finding issue. I'm not sure why it was disabled. The command used to work in 1.2.x |
Does anyone know how to actually fix this? Just disabling it for windows doesn't seem to resolve anything other than hiding a known issue. |
What I did was to setup the SIGINT event and when Control-C is triggered just call child.stop()
|
I am working in a Windows environment. In 1.2.3, when you hit control-c to exit the forever-monitor process, it also killed the child process. However, in 1.3.0, when you hit control-c, you only kill the forever-monitor process but the child process remains.
The text was updated successfully, but these errors were encountered: