From c1b83fcbc258fa0275b362a086db59e46597be09 Mon Sep 17 00:00:00 2001 From: willhayslett Date: Fri, 30 Mar 2018 16:49:57 -0500 Subject: [PATCH] doc: update to adding listens on SIGUSR1 Updated the doc/api/process.md documentation to reflect that listening on SIGUSR1 could impact the debugger. Fixes: https://github.com/nodejs/node/issues/19619 PR-URL: https://github.com/nodejs/node/pull/19709 Reviewed-By: Rich Trott Reviewed-By: Trivikram Kamat Reviewed-By: Ben Noordhuis Reviewed-By: James M Snell --- doc/api/process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/api/process.md b/doc/api/process.md index e524f3777af474..6d9e6f13f59967 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -366,7 +366,7 @@ process.on('SIGTERM', handle); ``` * `SIGUSR1` is reserved by Node.js to start the [debugger][]. It's possible to - install a listener but doing so will _not_ stop the debugger from starting. + install a listener but doing so might interfere with the debugger. * `SIGTERM` and `SIGINT` have default handlers on non-Windows platforms that reset the terminal mode before exiting with code `128 + signal number`. If one of these signals has a listener installed, its default behavior will be