aboutsummaryrefslogtreecommitdiffstats
path: root/man2/fdatasync.2
diff options
context:
space:
mode:
Diffstat (limited to 'man2/fdatasync.2')
-rw-r--r--man2/fdatasync.28
1 files changed, 4 insertions, 4 deletions
diff --git a/man2/fdatasync.2 b/man2/fdatasync.2
index 49cd2315c6..34fbbdbd2e 100644
--- a/man2/fdatasync.2
+++ b/man2/fdatasync.2
@@ -40,16 +40,16 @@ fdatasync \- synchronize a file's in-core data with that on disk
flushes all data buffers of a file to disk (before the system
call returns).
It resembles
-.BR fsync ()
+.BR fsync (2)
but is not required to update the metadata such as access time.
Applications that access databases or log files often write a tiny
data fragment (e.g., one line in a log file) and then call
-.BR fsync ()
+.BR fsync (2)
immediately in order to ensure that the written data is physically
stored on the harddisk.
Unfortunately,
-.BR fsync ()
+.BR fsync (2)
will always initiate two write operations: one for the newly written
data and another one in order to update the modification time stored
in the inode.
@@ -78,7 +78,7 @@ is bound to a special file which does not support synchronization.
Currently (Linux 2.2)
.BR fdatasync ()
is equivalent to
-.BR fsync ().
+.BR fsync (2).
.SH AVAILABILITY
On POSIX systems on which
.BR fdatasync ()