1 .\" Copyright (C) 1999 Andries Brouwer (aeb@cwi.nl)
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .\" Rewritten old page, 990824, aeb@cwi.nl
26 .\" 2004-12-14, mtk, added discussion of resolved_path == NULL
28 .TH REALPATH 3 2021-03-22 "" "Linux Programmer's Manual"
30 realpath \- return the canonicalized absolute pathname
33 .B #include <limits.h>
34 .B #include <stdlib.h>
36 .BI "char *realpath(const char *restrict " path ,
37 .BI " char *restrict " resolved_path );
41 Feature Test Macro Requirements for glibc (see
42 .BR feature_test_macros (7)):
48 .\" || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
49 || /* Glibc since 2.19: */ _DEFAULT_SOURCE
50 || /* Glibc <= 2.19: */ _BSD_SOURCE
54 expands all symbolic links and resolves references
58 characters in the null-terminated string named by
60 to produce a canonicalized absolute pathname.
61 The resulting pathname is stored as a null-terminated string,
65 in the buffer pointed to by
67 The resulting path will have no symbolic link,
75 is specified as NULL, then
79 to allocate a buffer of up to
81 bytes to hold the resolved pathname,
82 and returns a pointer to this buffer.
83 The caller should deallocate this buffer using
85 .\" Even if we use resolved_path == NULL, then realpath() will still
86 .\" return ENAMETOOLONG if the resolved pathname would exceed PATH_MAX
87 .\" bytes -- MTK, Dec 04
91 .\" function first appeared in 4.4BSD, contributed by Jan-Simon Pendry.
95 returns a pointer to the
98 Otherwise, it returns NULL, the contents
103 is set to indicate the error.
107 Read or search permission was denied for a component of the path prefix.
112 .\" (In libc5 this would just cause a segfault.)
113 (In glibc versions before 2.3,
114 this error is also returned if
119 An I/O error occurred while reading from the filesystem.
122 Too many symbolic links were encountered in translating the pathname.
125 A component of a pathname exceeded
127 characters, or an entire pathname exceeded
132 The named file does not exist.
138 A component of the path prefix is not a directory.
140 For an explanation of the terms used in this section, see
148 Interface Attribute Value
151 T} Thread safety MT-Safe
157 4.4BSD, POSIX.1-2001.
159 POSIX.1-2001 says that the behavior if
161 is NULL is implementation-defined.
162 POSIX.1-2008 specifies the behavior described in this page.
164 In 4.4BSD and Solaris, the limit on the pathname length is
166 (found in \fI<sys/param.h>\fP).
171 as found in \fI<limits.h>\fP or provided by the
174 A typical source fragment would be
181 path_max = pathconf(path, _PC_PATH_MAX);
188 (But see the BUGS section.)
190 .\" 2012-05-05, According to Casper Dik, the statement about
191 .\" Solaris was not true at least as far back as 1997, and
192 .\" may never have been true.
194 .\" The 4.4BSD, Linux and SUSv2 versions always return an absolute
196 .\" Solaris may return a relative pathname when the
198 .\" argument is relative.
201 .\" is given in \fI<unistd.h>\fP in libc4 and libc5,
202 .\" but in \fI<stdlib.h>\fP everywhere else.
204 If the call fails with either
210 is not NULL, then the prefix of
212 that is not readable or does not exist is returned in
215 The POSIX.1-2001 standard version of this function is broken by design,
216 since it is impossible to determine a suitable size for the output buffer,
218 According to POSIX.1-2001 a buffer of size
222 need not be a defined constant, and may have to be obtained using
226 does not really help, since, on the one hand POSIX warns that
229 may be huge and unsuitable for mallocing memory,
230 and on the other hand
232 may return \-1 to signify that
236 .I "resolved_path\ ==\ NULL"
237 feature, not standardized in POSIX.1-2001,
238 but standardized in POSIX.1-2008, allows this design problem to be avoided.
240 .\" The libc4 and libc5 implementation contained a buffer overflow
241 .\" (fixed in libc-5.4.13).
242 .\" Thus, set-user-ID programs like
244 .\" needed a private version.
248 .BR canonicalize_file_name (3),