diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2005-10-19 07:29:28 +0000 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2005-10-19 07:29:28 +0000 |
| commit | e1d6264d9feaed449e70f288ebdd40d8abae818c (patch) | |
| tree | c3c8c2c31ecf22c1e9cb32458e485d02a695d3c6 /man2/fdatasync.2 | |
| parent | f8fc5a2301bcf0cbfaa1db15adedde386e26a081 (diff) | |
| download | man-pages-e1d6264d9feaed449e70f288ebdd40d8abae818c.tar.gz | |
Manual fixes for parentheses formatting
Diffstat (limited to 'man2/fdatasync.2')
| -rw-r--r-- | man2/fdatasync.2 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man2/fdatasync.2 b/man2/fdatasync.2 index f720bac4bb..af9f2b4c9e 100644 --- a/man2/fdatasync.2 +++ b/man2/fdatasync.2 @@ -39,15 +39,15 @@ fdatasync \- synchronize a file's in-core data with that on disk .BR fdatasync () flushes all data buffers of a file to disk (before the system call returns). It resembles -.B fsync +.BR fsync () 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 -.B fsync +.BR fsync () immediately in order to ensure that the written data is physically stored on the harddisk. Unfortunately, -.B fsync +.BR fsync () 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. If the modification time is not a part of the transaction @@ -74,7 +74,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 (). .SH AVAILABILITY On POSIX systems on which .BR fdatasync () |