@ -1099,7 +1099,7 @@ changes:
Asynchronous lchmod(2). No arguments other than a possible exception
Asynchronous lchmod(2). No arguments other than a possible exception
are given to the completion callback.
are given to the completion callback.
Only available on Mac OS X .
Only available on macOS .
## fs.lchmodSync(path, mode)
## fs.lchmodSync(path, mode)
<!-- YAML
<!-- YAML
@ -1374,12 +1374,12 @@ The kernel ignores the position argument and always appends the data to
the end of the file.
the end of the file.
_Note: The behavior of `fs.open()` is platform specific for some flags. As such,
_Note: The behavior of `fs.open()` is platform specific for some flags. As such,
opening a directory on OS X and Linux with the `'a+'` flag - see example below -
opening a directory on mac OS and Linux with the `'a+'` flag - see example below -
will return an error. In contrast, on Windows and FreeBSD, a file descriptor
will return an error. In contrast, on Windows and FreeBSD, a file descriptor
will be returned._
will be returned._
```js
```js
// OS X and Linux
// mac OS and Linux
fs.open('< directory > ', 'a+', (err, fd) => {
fs.open('< directory > ', 'a+', (err, fd) => {
// => [Error: EISDIR: illegal operation on a directory, open < directory > ]
// => [Error: EISDIR: illegal operation on a directory, open < directory > ]
});
});
@ -1943,7 +1943,7 @@ Also note the listener callback is attached to the `'change'` event fired by
The `fs.watch` API is not 100% consistent across platforms, and is
The `fs.watch` API is not 100% consistent across platforms, and is
unavailable in some situations.
unavailable in some situations.
The recursive option is only supported on OS X and Windows.
The recursive option is only supported on mac OS and Windows.
#### Availability
#### Availability
@ -1954,7 +1954,7 @@ to be notified of filesystem changes.
* On Linux systems, this uses [`inotify`]
* On Linux systems, this uses [`inotify`]
* On BSD systems, this uses [`kqueue`]
* On BSD systems, this uses [`kqueue`]
* On OS X , this uses [`kqueue`] for files and [`FSEvents`] for directories.
* On mac OS, this uses [`kqueue`] for files and [`FSEvents`] for directories.
* On SunOS systems (including Solaris and SmartOS), this uses [`event ports`].
* On SunOS systems (including Solaris and SmartOS), this uses [`event ports`].
* On Windows systems, this feature depends on [`ReadDirectoryChangesW`].
* On Windows systems, this feature depends on [`ReadDirectoryChangesW`].
* On Aix systems, this feature depends on [`AHAFS`], which must be enabled.
* On Aix systems, this feature depends on [`AHAFS`], which must be enabled.
@ -1972,7 +1972,7 @@ less reliable.
<!-- type=misc -->
<!-- type=misc -->
On Linux and OS X systems, `fs.watch()` resolves the path to an [inode][] and
On Linux and mac OS systems, `fs.watch()` resolves the path to an [inode][] and
watches the inode. If the watched path is deleted and recreated, it is assigned
watches the inode. If the watched path is deleted and recreated, it is assigned
a new inode. The watch will emit an event for the delete but will continue
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.
watching the *original* inode. Events for the new inode will not be emitted.
@ -1982,7 +1982,7 @@ In AIX, save and close of a file being watched causes two notifications -
one for adding new content, and one for truncation. Moreover, save and
one for adding new content, and one for truncation. Moreover, save and
close operations on some platforms cause inode changes that force watch
close operations on some platforms cause inode changes that force watch
operations to become invalid and ineffective. AIX retains inode for the
operations to become invalid and ineffective. AIX retains inode for the
lifetime of a file, that way though this is different from Linux / OS X ,
lifetime of a file, that way though this is different from Linux / mac OS,
this improves the usability of file watching. This is expected behavior.
this improves the usability of file watching. This is expected behavior.
#### Filename Argument
#### Filename Argument