Explain how O_NOFOLLOW may cause EFTYPE. From joerg.

While here, sort errors. Bump date.
This commit is contained in:
wiz 2010-09-05 22:44:15 +00:00
parent bf2af3b9b5
commit d9898a950b

View File

@ -1,4 +1,4 @@
.\" $NetBSD: open.2,v 1.42 2010/05/31 12:16:20 njoly Exp $
.\" $NetBSD: open.2,v 1.43 2010/09/05 22:44:15 wiz Exp $
.\"
.\" Copyright (c) 1980, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -29,7 +29,7 @@
.\"
.\" @(#)open.2 8.2 (Berkeley) 11/16/93
.\"
.Dd April 3, 2010
.Dd September 5, 2010
.Dt OPEN 2
.Os
.Sh NAME
@ -258,6 +258,9 @@ were specified and the file exists.
.It Bq Er EFAULT
.Fa path
points outside the process's allocated address space.
.It Bq Er EFTYPE
.Dv O_NOFOLLOW
was specified, but the last path component is a symlink.
.It Bq Er EINTR
The
.Fn open
@ -279,12 +282,12 @@ A component of a pathname exceeded
characters, or an entire path name exceeded
.Brq Dv PATH_MAX
characters.
.It Bq Er ENFILE
The system file table is full.
.It Bq Er ENOENT
.Dv O_CREAT
is not set and the named file does not exist, or
a component of the path name that must exist does not exist.
.It Bq Er ENFILE
The system file table is full.
.It Bq Er ENOSPC
.Dv O_CREAT
is specified,