From fd9c8b37b5b3fe0995cf42184493f94d5062a2f2 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 6 Dec 2017 21:48:11 -0800 Subject: [PATCH] doc: immprove inode text in fs.md Rewrite and edit somewhat confusing paragraph about inodes and AIX in fs.md. PR-URL: https://github.com/nodejs/node/pull/17519 Reviewed-By: Jon Moss Reviewed-By: Anatoli Papirovski Reviewed-By: Richard Lau Reviewed-By: Luigi Pinca --- doc/api/fs.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/doc/api/fs.md b/doc/api/fs.md index e1ee8bc1e94286..9ea03f02748cbd 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -2491,12 +2491,9 @@ a new inode. The watch will emit an event for the delete but will continue watching the *original* inode. Events for the new inode will not be emitted. This is expected behavior. -On AIX, save and close of a file being watched causes two notifications - -one for adding new content, and one for truncation. Moreover, save and -close operations on some platforms cause inode changes that force watch -operations to become invalid and ineffective. AIX retains inode for the -lifetime of a file, that way though this is different from Linux / macOS, -this improves the usability of file watching. This is expected behavior. +AIX files retain the same inode for the lifetime of a file. Saving and closing a +watched file on AIX will result in two notifications (one for adding new +content, and one for truncation). #### Filename Argument