installs custom cleanup handlers that run on exiting node
npm install node-cleanup --save
nodeCleanup() installs functions that perform cleanup activities just before the node process exits. Let's call these functions "cleanup handlers." The cleanup handlers run under the following conditions:
- When the process exits normally (exit code 0).
- When the process exits due to an error, such as an uncaught exception (exit code 1).
- When the process receives one of the following POSIX signals: SIGINT (e.g. Ctrl-C), SIGHUP, SIGQUIT, or SIGTERM.
This solution has the following features:
- Allows cleanup handlers to behave as a function of exit code and signal.
- Allows multiple independent subsystems to install cleanup handlers.
- Allows for asynchronous cleanup on receiving a signal by postponing process termination.
- Allows for deferring to child processes the decision about whether a signal terminates the present process. For example, Emacs intercepts Ctrl-C, which should prevent its parent process from terminating.
- Allows for writing custom messages to
stderron SIGINT (e.g. Ctrl-C) and uncaught exceptions, regardless of the number of cleanup handlers installed. - Allows for uninstalling all cleanup handlers, such as to change termination behavior after having intercepted and cleaned up for a signal.
The module also has an extensive test suite to help ensure reliability.
Here is the typical way to use nodeCleanup():
var nodeCleanup = require('node-cleanup');
nodeCleanup(function (exitCode, signal) {
// release resources here before node exits
});If you only want to install your own messages for Ctrl-C and uncaught exception (either or both), you can do this:
nodeCleanup(null, {
ctrl_C: "{^C}",
uncaughtException: "Uh oh. Look what happened:"
});To get just the default stderr messages, without installing a cleanup handler:
nodeCleanup();You may also combine these to install a cleanup handler and stderr messages:
nodeCleanup(function (exitCode, signal) {
// release resources here before node exits
}, {
ctrl_C: "{^C}",
uncaughtException: "Uh oh. Look what happened:"
});You may perform asynchronous cleanup upon receiving a signal, as follows:
nodeCleanup(function (exitCode, signal) {
if (signal) {
unsavedData.save(function done() {
// calling process.exit() won't inform parent process of signal
process.kill(process.pid, signal);
});
nodeCleanup.uninstall(); // don't call cleanup handler again
return false;
}
});When you hit Ctrl-C, you send a SIGINT signal to each process in the current process group. A process group is set of processes that are all supposed to end together as a group instead of persisting independently. However, some programs, such as Emacs, intercept and repurpose SIGINT so that it does not end the process. In such cases, SIGINT should not end any processes of the group. Here is how you can delegate the decision to terminate to a child process:
var nodeCleanup = require('node-cleanup');
var fork = require('child_process').fork;
var child = fork('path-to-child-script.js');
child.on('exit', function (exitCode, signal) {
child = null; // enable the cleanup handler
if (signal === 'SIGINT')
process.kill(process.pid, 'SIGINT');
});
nodeCleanup(function (exitCode, signal) {
if (child !== null && signal === 'SIGINT')
return false; // don't exit yet
// release resources here before node exits
});nodeCleanup() has the following (FlowType) signature:
function nodeCleanup(cleanupHandler?: Function, messages?: object): voidnodeCleanup() installs a cleanup handler. It may also assign messages to write to stderr on SIGINT or an uncaught exception. Both parameters are optional. If not cleanupHandler is provided, the stderr messages are still written. If no messages are provided, default stderr messages are written. Calling nodeCleanup() with no parameters just installs these default messages.
cleanupHandler is a cleanup handler callback and is described in its own section below. When null or undefined, termination events all result in the process terminating, including signals.
messages is an object mapping any of the keys ctrl_C and uncaughtException to message strings that output to stderr. Default messages are provided for omitted messages. Set a message to the empty string '' inhibit the message.
nodeCleanup() may be called multiple times to install multiple cleanup handlers. Each of these handlers runs for each signal or termination condition. The first call to nodeCleanup() establishes the stderr messages; messages passed to subsequent calls are ignored.
nodeCleanup.uninstall() uninstalls all installed cleanup handlers and voids the stderr message assignments. It may be called multiple times without harm.
This function is primarily useful when a signal occurs and the cleanup handler performs cleanup but disables immediate process termination. In this case, when it is finally time to terminate the process, the cleanup handlers shouldn't run again, so the process uninstalls the handlers before terminating itself.
Each cleanup handler has the following (FlowType) signature:
function cleanupHandler(exitCode: number|null, signal: string|null): boolean?If the process is terminating for a reason other than a POSIX signal, exitCode is the exit code, and signal is null. Otherwise, if the process received a signal, signal is the signal's string name, and exitCode is null. These are the arguments passed to a child process exit event handler, mirrored here in node-cleanup for consistency.
Node.js defines these standard exit codes, but it does not appear to use code values >128 for signals. According to the node.js docs, these are the possible signals.
The return value of a cleanup handler is only significant for signals. If any cleanup handler returns a boolean false, the process does not exit. If they all return true (or for backwards compatibility, no return value), the process exits, reporting the signal to the parent process as the reason for the exit. The process always exits after calling the cleanup handlers for non-signals.
When a cleanup handler returns false to prevent the process from exiting, the cleanup handler normally takes steps to ensure proper termination later. For example, the process may wait for asynchronous cleanup to complete, or it may wait for a child process to signal termination. Normally in these cases the process would use nodeCleanup.uninstall() to uninstall the cleanup handlers prior to the second termination to prevent them from running again.
A cleanup handler should never call process.exit(). If a handler prevents a signal from terminating the process but later wishes to terminate the process for reason of this signal, the process should call process.kill(process.pid, signal). In particular, the process should not call process.exit(128 + signalNumber), because while this does communicate the exit code to the parent process, it does not communicate the exit signal by the means that the node.js child_process expects.
This module includes an extensive test suite. You can run it from the module directory with either the tap or subtap test runner, as follows:
sudo npm install -g tap
tap tests/*.js
or
sudo npm install -g subtap
subtap
(As of this writing, the test suite has only been run on a Mac. Behavior may vary from OS to OS, so I'm looking for feedback from other operating systems.)
TBD
- default messages
- catches SIGHUP, SIGQUIT, and SIGTERM
This module began by borrowing and modifying code from CanyonCasa's answer to a stackoverflow question. I had found the code necessary for all my node projects. @Banjocat piped in with a comment about how the solution didn't properly handle SIGINT. (See this detailed explanation of the SIGINT problem). I have completely rewritten the module to properly deal with SIGINT and other signals (I hope!). The rewrite also provides some additional flexibility that @zixia and I found ourselves needing for our respective projects.