Skip to content
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

nestd and host don't die when bash sends kill signal #1

Open
miyu opened this issue Jul 23, 2015 · 1 comment
Open

nestd and host don't die when bash sends kill signal #1

miyu opened this issue Jul 23, 2015 · 1 comment

Comments

@miyu
Copy link
Member

miyu commented Jul 23, 2015

Regression from previous behavior, pretty sure this has to do with the fact that nestd and host are now windows applications. Just a minor annoyance.

@miyu
Copy link
Member Author

miyu commented Nov 19, 2015

Probably not trivial to fix, especially since init.exe now launches nestd.

A potential workaround would send a shutdown signal to updated hatchlings, have nestd (which we shouldn't be touching too much) update to the development egg, then restart the hatchling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant