Skip to content

Commit

Permalink
Docs: Rephrase note about 32-bit timestamp precision issue (gulpjs#260)
Browse files Browse the repository at this point in the history
  • Loading branch information
erikkemperman authored and phated committed Jul 14, 2017
1 parent 71f1293 commit 2614fd7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ If they differ and the running process owns the file, the corresponding filesyst
If they don't differ or the process doesn't own the file, the attempt is skipped silently.
__This functionality is disabled on Windows operating systems or any other OS that doesn't support `process.getuid` or `process.geteuid` in node. This is due to Windows having very unexpected results through usage of `fs.fchmod` and `fs.futimes`.__

__Note: The `fs.futimes()` method internally casts `stat.mtime` and `stat.atime` to floats, which causes precision lost in 32bit Node.js.__
__Note: The `fs.futimes()` method internally converts `stat.mtime` and `stat.atime` timestamps to seconds; this division by `1000` may cause some loss of precision in 32-bit Node.js.__

If the file has a `symlink` attribute specifying a target path, then a symlink will be created.

Expand Down

0 comments on commit 2614fd7

Please sign in to comment.