1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: use consistent terminology in process doc

Browse Source 
`process.md` uses `POSIX` in most places, but `Unix` (and in one case
`Linux`) in a handful of cases where `POSIX` is appropriate. Change
those instances to `POSIX`.

PR-URL: https://github.com/nodejs/node/pull/15321
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This commit is contained in:
Rich Trott 2017-09-10 10:48:40 -07:00 committed by Ruben Bridgewater
parent 6cfd77338a
commit ff16337b80
No known key found for this signature in database
GPG Key ID: F07496B3EB3C1762
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/api/process.md
View File

@ -1673,10 +1673,10 @@ important ways:
2. They cannot be closed ([`end()`][] will throw). 2. They cannot be closed ([`end()`][] will throw).
3. They will never emit the [`'finish'`][] event. 3. They will never emit the [`'finish'`][] event.
4. Writes may be synchronous depending on the what the stream is connected to 4. Writes may be synchronous depending on the what the stream is connected to
and whether the system is Windows or Unix: and whether the system is Windows or POSIX:
- Files: *synchronous* on Windows and Linux - Files: *synchronous* on Windows and POSIX
- TTYs (Terminals): *asynchronous* on Windows, *synchronous* on Unix - TTYs (Terminals): *asynchronous* on Windows, *synchronous* on POSIX
- Pipes (and sockets): *synchronous* on Windows, *asynchronous* on Unix - Pipes (and sockets): *synchronous* on Windows, *asynchronous* on POSIX
These behaviors are partly for historical reasons, as changing them would These behaviors are partly for historical reasons, as changing them would
create backwards incompatibility, but they are also expected by some users. create backwards incompatibility, but they are also expected by some users.
@ -1859,7 +1859,7 @@ cases:
options were set, but the port number chosen was invalid or unavailable. options were set, but the port number chosen was invalid or unavailable.
* `>128` **Signal Exits** - If Node.js receives a fatal signal such as * `>128` **Signal Exits** - If Node.js receives a fatal signal such as
`SIGKILL` or `SIGHUP`, then its exit code will be `128` plus the `SIGKILL` or `SIGHUP`, then its exit code will be `128` plus the
value of the signal code. This is a standard Unix practice, since value of the signal code. This is a standard POSIX practice, since
exit codes are defined to be 7-bit integers, and signal exits set exit codes are defined to be 7-bit integers, and signal exits set
the high-order bit, and then contain the value of the signal code. the high-order bit, and then contain the value of the signal code.
For example, signal `SIGABRT` has value `6`, so the expected exit For example, signal `SIGABRT` has value `6`, so the expected exit