LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

Remove statement that (SYNC_FILE_RANGE_WAIT_BEFORE | 

SYNC_FILE_RANGE_WRITE | SYNC_FILE_RANGE_WAIT_AFTER) is
a traditional fdatasync(2) operation.
See https://bugzilla.mozilla.org/show_bug.cgi?id=421482 comments 129 to 131.
This commit is contained in:
Michael Kerrisk 2008-05-29 07:55:33 +00:00
parent bd4b0ce7d0
commit 7ce14e4094
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man2/sync_file_range.2
View File

@ -26,7 +26,7 @@
.\" 2006-07-05 Initial creation, Michael Kerrisk based on
.\" Andrew Morton's comments in fs/sync.c
.\"
.TH SYNC_FILE_RANGE 2 2006-07-05 "Linux" "Linux Programmer's Manual"
.TH SYNC_FILE_RANGE 2 2008-05-27 "Linux" "Linux Programmer's Manual"
.SH NAME
sync_file_range \- sync a file segment with disk
.SH SYNOPSIS
@ -118,11 +118,9 @@ This can be used after an earlier
.B SYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE
operation to wait for completion of that operation, and obtain its result.
.TP
.B SYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE | SYNC_FILE_RANGE_WAIT_AFTER
This is a traditional
.BR fdatasync (2)
operation.
It is a write-for-data-integrity operation
.B SYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE | \
SYNC_FILE_RANGE_WAIT_AFTER
This is a write-for-data-integrity operation
that will ensure that all pages in the specified range which were dirty when
.BR sync_file_range ()
was called are committed to disk.