mirror of https://github.com/mkerrisk/man-pages
open.2: Note ambiguity of ELOOP error when using O_NOFOLLOW
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
8db11e238b
commit
6ccb7137eb
|
@ -517,7 +517,11 @@ will not become the process's controlling terminal even if the
|
|||
process does not have one.
|
||||
.TP
|
||||
.B O_NOFOLLOW
|
||||
If \fIpathname\fP is a symbolic link, then the open fails.
|
||||
If \fIpathname\fP is a symbolic link, then the open fails, with the error
|
||||
.BR ELOOP .
|
||||
(Note that this is indistinguishable from the case where
|
||||
an open fails because there are too many symbolic links found
|
||||
while resolving components in the prefix part of the pathname.)
|
||||
This flag is a FreeBSD extension, which was added to Linux in version 2.1.126,
|
||||
and has subsequently been standardized in POSIX.1-2008.
|
||||
Symbolic links in earlier components of the pathname will still be
|
||||
|
|
Loading…
Reference in New Issue