Differences between current version and previous revision of fsync(2).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 4 | Last edited on Thursday, November 7, 2002 4:22:59 pm | by JohnMcPherson | |
Older page: | version 3 | Last edited on Thursday, November 7, 2002 12:19:21 am | by PerryLorier | Revert |
@@ -25,8 +25,10 @@
When an ext2 file system is mounted with the ''sync'' option, directory entries are also implicitely synced by fsync(2).
On kernels before 2.4, fsync(2) on big files can be inefficient. An alternative might be to use the ''O_SYNC'' flag to open(2).
!!CONFORMING TO
-POSIX.1b (formerly POSIX.4)
+[
POSIX]
.1b (formerly [
POSIX]
.4)
!!SEE ALSO
bdflush(2), open(2), sync(2), mount(8), update(8), sync(8), fdatasync(2)
+----
+The difference between fsync(2) and fdatasync(2) is that fsync modifies the access time metadata in the i-node, while fdatasync doesn't/shouldn't. I think this is true version kernel versions >= 2.4 - for 2.2 and earlier fdatasync was the same as fsync.