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

Process death handling #85

Open
rhyslbw opened this issue Mar 29, 2016 · 1 comment
Open

Process death handling #85

rhyslbw opened this issue Mar 29, 2016 · 1 comment

Comments

@rhyslbw
Copy link
Member

rhyslbw commented Mar 29, 2016

In #43 I raised the option of using winston to catch unhandled exceptions, however there are more things to consider like process exit events in order to gain proper control of the production system and perform a graceful shutdown. I've been using an npm package called death that we could use as infrastructure, and then use the module lifecycle hook to allow implementations to define shutdown code.

@rhyslbw
Copy link
Member Author

rhyslbw commented Apr 4, 2016

This would actually be a good way to help shield from sloppy implementation of a process.on('uncaughtException'), as we could call the app's shutdown hook then process.exit along with a log entry

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