src/lib/libc/sys/msync.2, branch release/11.1.0

msync(2) must return ENOMEM and not EINVAL when the address is outside the

2014-05-07T08:38:02+00:00

allowed range or when one or more pages are not mapped. This according to
The Open Group Base Specifications Issue 7.

Discussed with:	 attilio, Bruce Evans
Reviewed by:	 alc, Garrett Cooper
Reported by:	 ATF
MFC after:	 2 weeks
Sponsored by:	EMC / Isilon storage division

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

2012-03-17T23:55:18+00:00

Document EIO from msync(2).

Inspired by PR:	 docs/165929 [1]
Reviewed by:	 jilles
MFC after:	 2 weeks

Per Regents of the University of Calfornia letter, remove advertising

2007-01-09T00:28:16+00:00

clause.

# If I've done so improperly on a file, please let me know.

Add a BUGS section and copy the wording from mmap(2)'s MAP_NOSYNC,

2004-09-03T06:24:25+00:00

documenting the obsoleteness of the msync(2) syscall and its single
remaining purpose.

PR:		70916
Submitted by:	Radim Kolar 
MFC after:	3 days

Markup, grammar, and spelling fixes.

2004-06-30T20:09:10+00:00

- Add documentation for EBUSY.

2003-11-14T07:18:12+00:00

 - Remove EIO.
 - Add a cross reference to mlock(2).

mdoc(7) police: "The .Fa argument.".

2002-12-19T09:40:28+00:00

mdoc(7) police: Tidy up the syscall language.

2002-12-18T09:22:32+00:00

Stop calling system calls "function calls".

Use "The .Fn system call" a-la "The .Nm utility".

When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.

Uniformly refer to a file system as "file system".

2002-12-12T17:26:04+00:00

Approved by:	re

Note that in no longer a prerequisite for and

2002-08-24T00:39:43+00:00