Remove ambiguity in description of support for O_EXCL on NFS.

As per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491791.
This commit is contained in:
Michael Kerrisk 2008-07-22 05:48:27 +00:00
parent 21dcaf8b91
commit bbae62c333
1 changed files with 2 additions and 3 deletions

View File

@ -47,7 +47,7 @@
.\" FIXME . Apr 08: The next POSIX revision has O_EXEC, O_SEARCH, and
.\" O_TTYINIT. Eventually these may need to be documented. --mtk
.\"
.TH OPEN 2 2008-07-04 "Linux" "Linux Programmer's Manual"
.TH OPEN 2 2008-07-22 "Linux" "Linux Programmer's Manual"
.SH NAME
open, creat \- open and possibly create a file or device
.SH SYNOPSIS
@ -316,8 +316,7 @@ is a symbolic link, then
fails regardless of where the symbolic link points to.
.B O_EXCL
is not supported on NFSv2 or on Linux before kernel 2.6;
it is supported on Linux 2.6 and later, with NFSv3 or later.
is only supported on NFS when using NFSv3 or later on kernel 2.6 or later.
In environments where NFS
.B O_EXCL
support is not provided, programs that rely on it