From dac1d38a02398d65615496b1679cb071ff45a4f0 Mon Sep 17 00:00:00 2001 From: Ben Noordhuis Date: Sun, 4 Oct 2015 00:15:08 +0200 Subject: [PATCH] doc: stdout/stderr can block when directed to file Update the documentation for `process.stdout` and `process.stdout` to clarify that writes can block when stdio is redirected to a file. In all other cases, it's non-blocking. PR-URL: https://github.com/nodejs/node/pull/3170 Reviewed-By: Jeremiah Senkpiel --- doc/api/process.markdown | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/doc/api/process.markdown b/doc/api/process.markdown index eecf494c48bf27..0c32799a66b6c6 100644 --- a/doc/api/process.markdown +++ b/doc/api/process.markdown @@ -282,7 +282,9 @@ For example, a `console.log` equivalent could look like this: `process.stderr` and `process.stdout` are unlike other streams in Node.js in that they cannot be closed (`end()` will throw), they never emit the `finish` -event and that writes are always blocking. +event and that writes can block when output is redirected to a file (although +disks are fast and operating systems normally employ write-back caching so it +should be a very rare occurrence indeed.) To check if Node.js is being run in a TTY context, read the `isTTY` property on `process.stderr`, `process.stdout`, or `process.stdin`: @@ -305,14 +307,9 @@ A writable stream to stderr (on fd `2`). `process.stderr` and `process.stdout` are unlike other streams in Node.js in that they cannot be closed (`end()` will throw), they never emit the `finish` -event and that writes are usually blocking. - -- They are blocking in the case that they refer to regular files or TTY file - descriptors. -- In the case they refer to pipes: - - They are blocking in Linux/Unix. - - They are non-blocking like other streams in Windows. - +event and that writes can block when output is redirected to a file (although +disks are fast and operating systems normally employ write-back caching so it +should be a very rare occurrence indeed.) ## process.stdin