realpath.3: Fix EINVAL error

Since glibc 2.3, resolved_path can be non-NULL (with the
semantics already documented in the page).

Reported-by: Seonghun Lim <wariua@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2011-09-09 20:08:24 +02:00
parent ec3cf7a42e
commit 536bc96676
1 changed files with 6 additions and 6 deletions

View File

@ -23,7 +23,7 @@
.\" Rewritten old page, 990824, aeb@cwi.nl
.\" 2004-12-14, mtk, added discussion of resolved_path == NULL
.\"
.TH REALPATH 3 2010-09-20 "" "Linux Programmer's Manual"
.TH REALPATH 3 2011-09-10 "" "Linux Programmer's Manual"
.SH NAME
realpath \- return the canonicalized absolute pathname
.SH SYNOPSIS
@ -104,13 +104,13 @@ is set to indicate the error.
Read or search permission was denied for a component of the path prefix.
.TP
.B EINVAL
Either
.I path
or
.I resolved_path
is NULL.
(In libc5 this would just cause a segfault.)
But, see NOTES below.
.\" (In libc5 this would just cause a segfault.)
(In glibc versions before 2.3,
this error is also returned if
.IR resolved_path
is NULL.)
.TP
.B EIO
An I/O error occurred while reading from the file system.