Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 70c95ea

Browse filesBrowse files
r-52Myles Borins
authored andcommitted
doc: add warning about Windows process groups
This commit adds a warning for Windows platforms. `process.kill` wont kill a process group on Windows and instead it throws an error. Refs: #3617 PR-URL: #3681 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
1 parent e6c2533 commit 70c95ea
Copy full SHA for 70c95ea

File tree

Expand file treeCollapse file tree

1 file changed

+2
-1
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-1
lines changed
Open diff view settings
Collapse file

‎doc/api/process.markdown‎

Copy file name to clipboardExpand all lines: doc/api/process.markdown
+2-1Lines changed: 2 additions & 1 deletion
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -547,7 +547,8 @@ string describing the signal to send. Signal names are strings like
547547
See [Signal Events][] and kill(2) for more information.
548548

549549
Will throw an error if target does not exist, and as a special case, a signal
550-
of `0` can be used to test for the existence of a process.
550+
of `0` can be used to test for the existence of a process. Windows platforms
551+
will throw an error if the `pid` is used to kill a process group.
551552

552553
Note that even though the name of this function is `process.kill`, it is really
553554
just a signal sender, like the `kill` system call. The signal sent may do

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.