Skip to content

doc: clarify signal listener behavior #65243

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.

Sign up for GitHub

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

Open
SomSamantray wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −1
Open

doc: clarify signal listener behavior #65243

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion doc/api/process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -669,7 +669,8 @@ process.on('SIGTERM', handle);
* `'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
removed (Node.js will no longer exit).
removed. Signal events are emitted asynchronously, so Node.js may exit before
the listener is called if the event loop is otherwise empty.
* `'SIGPIPE'` is ignored by default. It can have a listener installed.
* `'SIGHUP'` is generated on Windows when the console window is closed, and on
other platforms under various similar conditions. See signal(7). It can have a
Expand Down
Loading