Commit c1b83fc
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: #19619
PR-URL: #19709
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent e0c7d78 commit c1b83fc
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -366,7 +366,7 @@ process.on('SIGTERM', handle); | |||
| 366 | 366 | ``` | |
| 367 | 367 | ||
| 368 | 368 | * `SIGUSR1` is reserved by Node.js to start the [debugger][]. It's possible to | |
| 369 | - install a listener but doing so will _not_ stop the debugger from starting. | ||
| 369 | + install a listener but doing so might interfere with the debugger. | ||
| 370 | 370 | * `SIGTERM` and `SIGINT` have default handlers on non-Windows platforms that | |
| 371 | 371 | reset the terminal mode before exiting with code `128 + signal number`. If one | |
| 372 | 372 | of these signals has a listener installed, its default behavior will be | |
0 commit comments