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

Ensure Trinity handles SIGTERM send to main process #1465

Merged
merged 1 commit into from Nov 12, 2018

Conversation

cburgdorf
Copy link
Contributor

@cburgdorf cburgdorf commented Nov 12, 2018

What was wrong?

Currently, when sending a SIGTERM to the Trinity
main process, Trinity doesn't shut down gracefully.
The main process shuts down but the child processes
doesn't.

This can easily be reproduced:

  1. Run trinity

  2. Take note of the pid printed as Started main process (pid=<pid-to-note>)

  3. Open another terminal and run `kill

Notice that the main process is killed but the child processes keep on running.

How was it fixed?

This change does two things:

  • print out the main process id at boot
  • handle SIGTERM correctly

Relates to #1461

Cute Animal Picture

put a cute animal picture link inside the parentheses

Currently, when sending a SIGTERM to the Trinity
main process, Trinity doesn't shut down gracefully.
The main process shuts down but the child processes
doesn't.

This change does two things:
  - print out the main process id at boot
  - handle SIGTERM correctly

Relates to #1461
@cburgdorf cburgdorf merged commit 9a9ad1d into ethereum:master Nov 12, 2018
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.

None yet

2 participants