Skip to content

fix ugly error message when killing commands #1064

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

Merged
merged 1 commit into from
Apr 12, 2015
Merged

Conversation

whyrusleeping
Copy link
Member

This prevents the commands client from trying to open a node when communicating with the daemon. Although it still prints:

Received interrupt signal, shutting down...

Which I am not sure I want printed clientside

also, addresses #1053

@whyrusleeping whyrusleeping added the status/in-progress In progress label Apr 12, 2015
@jbenet
Copy link
Member

jbenet commented Apr 12, 2015

LGTM. waiting on tests

jbenet added a commit that referenced this pull request Apr 12, 2015
fix ugly error message when killing commands
@jbenet jbenet merged commit 730b00b into master Apr 12, 2015
@jbenet jbenet removed the status/in-progress In progress label Apr 12, 2015
@jbenet jbenet deleted the fix/interupt-error branch April 12, 2015 22:35
@torarnv
Copy link
Contributor

torarnv commented Apr 14, 2015

I'm confused by this PR, the fix seems to be so sweeping that we've stopped cleaning up at shutdown. See #1081

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.

3 participants