open.2: Remove ambiguity in text on NFS and O_EXCL.

Reported-by: David Sommerseth <davids@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2010-06-14 04:38:26 +02:00
parent 14f1e036e1
commit efe08656e6
1 changed files with 4 additions and 3 deletions

View File

@ -48,7 +48,7 @@
.\" O_TTYINIT. Eventually these may need to be documented. --mtk
.\" FIXME Linux 2.6.33 has O_DSYNC, and a hiddden __O_SYNC.
.\"
.TH OPEN 2 2009-09-20 "Linux" "Linux Programmer's Manual"
.TH OPEN 2 2010-06-14 "Linux" "Linux Programmer's Manual"
.SH NAME
open, creat \- open and possibly create a file or device
.SH SYNOPSIS
@ -333,9 +333,10 @@ is a symbolic link, then
.BR open ()
fails regardless of where the symbolic link points to.
On NFS,
.B O_EXCL
is only supported on NFS when using NFSv3 or later on kernel 2.6 or later.
In environments where NFS
is only supported when using NFSv3 or later on kernel 2.6 or later.
In NFS environments where
.B O_EXCL
support is not provided, programs that rely on it
for performing locking tasks will contain a race condition.