|RENAME(2)||Linux Programmer's Manual||RENAME(2)|
NAME¶rename, renameat, renameat2 - change the name or location of a file
#include <stdio.h>int rename(const char *oldpath, const char *newpath);#include <fcntl.h> /* Definition of AT_* constants */ #include <stdio.h>int renameat(int olddirfd, const char *oldpath, int newdirfd, const char *newpath); int renameat2(int olddirfd, const char *oldpath, int newdirfd, const char *newpath, unsigned int flags);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
- Since glibc 2.10:
- _POSIX_C_SOURCE >= 200809L
- Before glibc 2.10:
DESCRIPTION¶rename() renames a file, moving it between directories if required. Any other hard links to the file (as created using link(2)) are unaffected. Open file descriptors for oldpath are also unaffected.
renameat()¶The renameat() system call operates in exactly the same way as rename(), except for the differences described here.
renameat2()¶renameat2() has an additional flags argument. A renameat2() call with a zero flags argument is equivalent to renameat().
- Atomically exchange oldpath and newpath. Both pathnames must exist but may be of different types (e.g., one could be a non-empty directory and the other a symbolic link).
- Don't overwrite newpath of the rename. Return an
error if newpath already exists.
- RENAME_WHITEOUT (since Linux 3.18)
- This operation makes sense only for overlay/union
RETURN VALUE¶On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
- Write permission is denied for the directory containing oldpath or newpath, or, search permission is denied for one of the directories in the path prefix of oldpath or newpath, or oldpath is a directory and does not allow write permission (needed to update the .. entry). (See also path_resolution(7).)
- The rename fails because oldpath or newpath is a directory that is in use by some process (perhaps as current working directory, or as root directory, or because it was open for reading) or is in use by the system (for example as mount point), while the system considers this an error. (Note that there is no requirement to return EBUSY in such cases—there is nothing wrong with doing the rename anyway—but it is allowed to return EBUSY if the system cannot otherwise handle such situations.)
- The user's quota of disk blocks on the filesystem has been exhausted.
- oldpath or newpath points outside your accessible address space.
- The new pathname contained a path prefix of the old, or, more generally, an attempt was made to make a directory a subdirectory of itself.
- newpath is an existing directory, but oldpath is not a directory.
- Too many symbolic links were encountered in resolving oldpath or newpath.
- oldpath already has the maximum number of links to it, or it was a directory and the directory containing newpath has the maximum number of links.
- oldpath or newpath was too long.
- The link named by oldpath does not exist; or, a directory component in newpath does not exist; or, oldpath or newpath is an empty string.
- Insufficient kernel memory was available.
- The device containing the file has no room for the new directory entry.
- A component used as a directory in oldpath or newpath is not, in fact, a directory. Or, oldpath is a directory, and newpath exists but is not a directory.
- ENOTEMPTY or EEXIST
- newpath is a nonempty directory, that is, contains entries other than "." and "..".
- EPERM or EACCES
- The directory containing oldpath has the sticky bit (S_ISVTX) set and the process's effective user ID is neither the user ID of the file to be deleted nor that of the directory containing it, and the process is not privileged (Linux: does not have the CAP_FOWNER capability); or newpath is an existing file and the directory containing it has the sticky bit set and the process's effective user ID is neither the user ID of the file to be replaced nor that of the directory containing it, and the process is not privileged (Linux: does not have the CAP_FOWNER capability); or the filesystem containing pathname does not support renaming of the type requested.
- The file is on a read-only filesystem.
- oldpath and newpath are not on the same mounted filesystem. (Linux permits a filesystem to be mounted at multiple points, but rename() does not work across different mount points, even if the same filesystem is mounted on both.)
- olddirfd or newdirfd is not a valid file descriptor.
- oldpath is relative and olddirfd is a file descriptor referring to a file other than a directory; or similar for newpath and newdirfd
- flags contains RENAME_NOREPLACE and newpath already exists.
- An invalid flag was specified in flags.
- Both RENAME_NOREPLACE and RENAME_EXCHANGE were specified in flags.
- Both RENAME_WHITEOUT and RENAME_EXCHANGE were specified in flags.
- The filesystem does not support one of the flags in flags.
- flags contains RENAME_EXCHANGE and newpath does not exist.
- RENAME_WHITEOUT was specified in flags, but the caller does not have the CAP_MKNOD capability.
VERSIONS¶renameat() was added to Linux in kernel 2.6.16; library support was added to glibc in version 2.4.
CONFORMING TO¶rename(): 4.3BSD, C89, C99, POSIX.1-2001, POSIX.1-2008.
Glibc notes¶On older kernels where renameat() is unavailable, the glibc wrapper function falls back to the use of rename(). When oldpath and newpath are relative pathnames, glibc constructs pathnames based on the symbolic links in /proc/self/fd that correspond to the olddirfd and newdirfd arguments.
BUGS¶On NFS filesystems, you can not assume that if the operation failed, the file was not renamed. If the server does the rename operation and then crashes, the retransmitted RPC which will be processed when the server is up again causes a failure. The application is expected to deal with this. See link(2) for a similar problem.
SEE ALSO¶mv(1), chmod(2), link(2), symlink(2), unlink(2), path_resolution(7), symlink(7)
COLOPHON¶This page is part of release 4.10 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.