1 .\" Hey Emacs! This file is -*- nroff -*- source.
3 .\" This manpage is Copyright (C) 2006, Michael Kerrisk
5 .\" Permission is granted to make and distribute verbatim copies of this
6 .\" manual provided the copyright notice and this permission notice are
7 .\" preserved on all copies.
9 .\" Permission is granted to copy and distribute modified versions of this
10 .\" manual under the conditions for verbatim copying, provided that the
11 .\" entire resulting derived work is distributed under the terms of a
12 .\" permission notice identical to this one.
14 .\" Since the Linux kernel and libraries are constantly changing, this
15 .\" manual page may be incorrect or out-of-date. The author(s) assume no
16 .\" responsibility for errors or omissions, or for damages resulting from
17 .\" the use of the information contained herein. The author(s) may not
18 .\" have taken the same level of care in the production of this manual,
19 .\" which is licensed free of charge, as they might when working
22 .\" Formatted or processed versions of this manual, if unaccompanied by
23 .\" the source, must acknowledge the copyright and authors of this work.
26 .TH OPENAT 2 2006-03-06 "Linux 2.6.16" "Linux Programmer's Manual"
28 openat \- open a file at a relative location
31 .B #include <sys/types.h>
32 .B #include <sys/stat.h>
35 .BI "int openat(int " dirfd ", const char *" pathname ", int " flags );
36 .BI "int openat(int " dirfd ", const char *" pathname ", int " flags \
42 system call operates in exactly the same way as
44 except for the differences described in this manual page.
46 If the pathname given in
48 is relative, then it is interpreted relative to the directory
49 referred to by the file descriptor
51 (rather than relative to the current working directory of
52 the calling process, as is done by
54 for a relative pathname).
56 If the pathname given in
62 then pathname is interpreted relative to the current working
63 directory of the calling process (like
66 If the pathname given in
73 returns a new file descriptor, or \-1 if an error occurred
76 is set appropriately).
78 The same errors that occur for
82 The following additional errors can occur for
87 is not a valid file descriptor.
91 is a file descriptor referring to a file other than a directory.
95 system call (and similar system calls suffixed "at")
96 provides functionality that can otherwise only be obtained
97 less efficiently or at the risk of races in user applications.
98 It allows the implementation of a per-thread "current working
99 directory", via file descriptor(s) maintained by the application.
100 (This functionality can also be obtained by tricks based
102 .IR /proc/self/fd/ dirfd,
103 but less efficiently.)
104 It also allows the avoidance of various kinds of races that can occur
105 as a result of directory deletions that may occur while an application
106 is traversing a file system.
108 This system call is non-standard.
109 A similar system call exists on Solaris.
110 .\" The 'at' suffix in Solaris is actually double sensed. It
111 .\" primarily referred to "extended *at*tributes", which are
112 .\" handled by Solaris' O_XATTR flag, but was also intended
113 .\" to refer to the notion of "at a relative location".
115 .\" See also the following for a discussion of the inconsistent
116 .\" naming of the *at() functions:
117 .\" http://www.opengroup.org/austin/mailarchives/ag/msg09103.html
118 .\" Subject: RE: The naming of at()s is a difficult matter
120 .\" Date: Tue, 14 Feb 2006 14:56:50 -0800 (PST)
124 was added to Linux in kernel 2.6.16.
127 .BR path_resolution (2)