Do not claim that msync(2) is obsoleted [1].

Document EIO from msync(2).

Inspired by PR:	 docs/165929 [1]
Reviewed by:	 jilles
MFC after:	 2 weeks
This commit is contained in:
Konstantin Belousov 2012-03-17 23:55:18 +00:00
parent a53373fabe
commit 1d73bec4c1
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=233102
2 changed files with 7 additions and 4 deletions

View file

@ -28,7 +28,7 @@
.\" @(#)mmap.2 8.4 (Berkeley) 5/11/95
.\" $FreeBSD$
.\"
.Dd August 28, 2010
.Dd March 18, 2012
.Dt MMAP 2
.Os
.Sh NAME
@ -205,7 +205,7 @@ command and
system call generally do not flush dirty NOSYNC VM data.
The
.Xr msync 2
system call is obsolete since
system call is usually not needed since
.Bx
implements a coherent file system buffer cache.
However, it may be

View file

@ -28,7 +28,7 @@
.\" @(#)msync.2 8.2 (Berkeley) 6/21/94
.\" $FreeBSD$
.\"
.Dd June 21, 1994
.Dd March 18, 2012
.Dt MSYNC 2
.Os
.Sh NAME
@ -98,6 +98,9 @@ The
argument
was both MS_ASYNC and MS_INVALIDATE.
Only one of these flags is allowed.
.It Bq Er EIO
An error occurred while writing at least one of the pages in
the specified region.
.El
.Sh SEE ALSO
.Xr madvise 2 ,
@ -113,7 +116,7 @@ system call first appeared in
.Sh BUGS
The
.Fn msync
system call is obsolete since
system call is usually not needed since
.Bx
implements a coherent file system buffer cache.
However, it may be used to associate dirty VM pages with file system