fsync.2: Minor clean-ups of Christoph's patch

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2012-02-27 13:13:50 +13:00
parent 71ae2f4a3f
commit ad4760331e
1 changed files with 6 additions and 5 deletions

View File

@ -33,8 +33,9 @@
.\" Modified 18 Apr 2001 by Andi Kleen
.\" Fix description to describe what it really does; add a few caveats.
.\" 2006-04-28, mtk, substantial rewrite of various parts.
.\" 2012-02-27 Various changes by Christoph Hellwig <hch@lst.de>
.\"
.TH FSYNC 2 2008-11-07 "Linux" "Linux Programmer's Manual"
.TH FSYNC 2 2012-02-27 "Linux" "Linux Programmer's Manual"
.SH NAME
fsync, fdatasync \- synchronize a file's in-core state with storage device
.SH SYNOPSIS
@ -65,8 +66,8 @@ file referred to by the file descriptor
.I fd
to the disk device (or other permanent storage device) so that all
changed information can be retrieved even after the system crashed or
was rebooted. This includes writing through or flushing a disk cache
if present.
was rebooted.
This includes writing through or flushing a disk cache if present.
The call blocks until the device reports that the transfer has completed.
It also flushes metadata information associated with the file (see
.BR stat (2)).
@ -147,8 +148,8 @@ and so has no performance advantage.
The
.BR fsync ()
implementations in older kernels and lesser used filesystems
does not know how to flush disk caches. In these cases disk caches need to
be disabled using
does not know how to flush disk caches.
In these cases disk caches need to be disabled using
.BR hdparm (8)
or
.BR sdparm (8)