Section: Linux Programmer's Manual (3)
realpath - return the canonicalized absolute pathname
char *realpath(const char *path, char *resolved_path);
Feature Test Macro Requirements for glibc (see
_XOPEN_SOURCE >= 500
|| /* Glibc since 2.19: */ _DEFAULT_SOURCE
|| /* Glibc versions <= 2.19: */ _BSD_SOURCE
expands all symbolic links and resolves references
and extra '/'
characters in the null-terminated string named by
to produce a canonicalized absolute pathname.
The resulting pathname is stored as a null-terminated string,
up to a maximum of
in the buffer pointed to by
The resulting path will have no symbolic link,
is specified as NULL, then
to allocate a buffer of up to
bytes to hold the resolved pathname,
and returns a pointer to this buffer.
The caller should deallocate this buffer using
If there is no error,
returns a pointer to the
Otherwise, it returns NULL, the contents
of the array
are undefined, and
is set to indicate the error.
Read or search permission was denied for a component of the path prefix.
(In glibc versions before 2.3,
this error is also returned if
An I/O error occurred while reading from the filesystem.
Too many symbolic links were encountered in translating the pathname.
A component of a pathname exceeded
characters, or an entire pathname exceeded
The named file does not exist.
Out of memory.
A component of the path prefix is not a directory.
For an explanation of the terms used in this section, see
POSIX.1-2001 says that the behavior if
is NULL is implementation-defined.
POSIX.1-2008 specifies the behavior described in this page.
In 4.4BSD and Solaris, the limit on the pathname length is
(found in <sys/param.h>
as found in <limits.h>
or provided by the
A typical source fragment would be
path_max = PATH_MAX;
path_max = pathconf(path, _PC_PATH_MAX);
if (path_max <= 0)
path_max = 4096;
(But see the BUGS section.)
If the call fails with either
is not NULL, then the prefix of
that is not readable or does not exist is returned in
The POSIX.1-2001 standard version of this function is broken by design,
since it is impossible to determine a suitable size for the output buffer,
According to POSIX.1-2001 a buffer of size
need not be a defined constant, and may have to be obtained using
does not really help, since, on the one hand POSIX warns that
the result of
may be huge and unsuitable for mallocing memory,
and on the other hand
may return -1 to signify that
is not bounded.
resolved_path == NULL
feature, not standardized in POSIX.1-2001,
but standardized in POSIX.1-2008, allows this design problem to be avoided.
This page is part of release 5.04 of the Linux
A description of the project,
information about reporting bugs,
and the latest version of this page,
can be found at