1 .\" Copyright (c) 1983, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)rename.2 8.1 (Berkeley) 6/4/93
35 .Nd change the name of a file
41 .Fn rename "const char *from" "const char *to"
43 .Fn renameat "int fromfd" "const char *from" "int tofd" "const char *to"
54 exists, it is first removed.
59 must be of the same type (that is, both directories or both
60 non-directories), and must reside on the same file system.
67 already exists, an instance of
69 will always exist, even if the system should crash in
70 the middle of the operation.
72 If the final component of
75 the symbolic link is renamed,
76 not the file or directory to which it points.
82 resolve to the same directory entry, or to different directory
83 entries for the same existing file,
85 returns success without taking any further action.
89 system call is equivalent to
91 except in the case where either
95 specifies a relative path.
98 is a relative path, the file to be renamed is located
99 relative to the directory associated with the file descriptor
101 instead of the current working directory.
104 is a relative path, the same happens only relative to the directory associated
109 is passed the special value
115 parameter, the current working directory is used in the determination
116 of the file for the respective path parameter.
118 .\"The system can deadlock if a loop in the file system graph is present.
119 .\"This loop takes the form of an entry in directory
123 .\"being a hard link to directory
133 .\"When such a loop exists and two separate processes attempt to
135 .\".Ql rename a/foo b/bar
137 .\".Ql rename b/bar a/foo ,
139 .\"the system may deadlock attempting to lock
140 .\"both directories for modification.
141 .\"Hard links to directories should be
142 .\"replaced by symbolic links by the system administrator.
149 will fail and neither of the argument files will be
152 .It Bq Er ENAMETOOLONG
153 A component of either pathname exceeded 255 characters,
154 or the entire length of either path name exceeded 1023 characters.
163 A component of either path prefix denies search permission.
165 The requested link requires writing in a directory with a mode
166 that denies write permission.
168 The directory pointed at by the
170 argument denies write permission, and the operation would move
171 it to another parent directory.
173 The file pointed at by the
175 argument has its immutable, undeletable or append-only flag set, see the
177 manual page for more information.
179 The parent directory of the file pointed at by the
181 argument has its immutable or append-only flag set.
183 The parent directory of the file pointed at by the
185 argument has its immutable flag set.
187 The directory containing
190 and neither the containing directory nor
192 are owned by the effective user ID.
194 The file pointed at by the
198 the directory containing
201 and neither the containing directory nor
203 are owned by the effective user ID.
205 Too many symbolic links were encountered in translating either pathname.
207 A component of either path prefix is not a directory.
225 and the file named by
227 are on different logical devices (file systems).
229 code will not be returned if the implementation permits cross-device
232 The directory in which the entry for the new name is being placed
233 cannot be extended because there is no space left on the file
234 system containing the directory.
236 The directory in which the entry for the new name
237 is being placed cannot be extended because the
238 user's quota of disk blocks on the file system
239 containing the directory has been exhausted.
241 An I/O error occurred while making or updating a directory entry.
243 Corrupted data was detected while reading from the file system.
245 The requested link requires writing in a directory on a read-only file
249 points outside the process's allocated address space.
254 is a parent directory of
256 or an attempt is made to rename
264 is a directory and is not empty.
267 was called and the process is in capability mode.
270 In addition to the errors returned by the
279 argument does not specify an absolute path and the
283 nor a valid file descriptor open for searching, or the
285 argument does not specify an absolute path and the
289 nor a valid file descriptor open for searching.
293 argument is not an absolute path and
297 nor a file descriptor associated with a directory, or the
299 argument is not an absolute path and
303 nor a file descriptor associated with a directory.
306 is specified and the process is in capability mode.
307 .It Bq Er ENOTCAPABLE
309 is an absolute path or contained a ".." component leading to a directory
310 outside of the directory hierarchy specified by
314 .It Bq Er ENOTCAPABLE
317 file descriptor lacks the
318 .Dv CAP_RENAMEAT_SOURCE
321 file descriptor lacks the
322 .Dv CAP_RENAMEAT_TARGET
332 system call is expected to conform to
336 system call follows The Open Group Extended API Set 2 specification.
340 system call appeared in