PROLOG<\/a> This manual page is part of the POSIX Programmer\u2019s Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.<\/p>\n rename, renameat \u2014 rename file<\/p>\n #include int rename(const char *old<\/i>, const char *new<\/i>);<\/p>\n #include int renameat(int oldfd<\/i>, const char *old<\/i>, int newfd<\/i>, For rename<\/i>(): The functionality described on this reference page is aligned with the ISO\u00a0C standard. Any conflict between the requirements described here and the ISO\u00a0C standard is unintentional. This volume of POSIX.1-2017 defers to the ISO\u00a0C standard.<\/p>\n The rename<\/i>() function shall change the name of a file. The old<\/i> argument points to the pathname of the file to be renamed. The new<\/i> argument points to the new pathname of the file. If the new<\/i> argument does not resolve to an existing directory entry for a file of type directory and the new<\/i> argument contains at least one non- If either the old<\/i> or new<\/i> argument names a symbolic link, rename<\/i>() shall operate on the symbolic link itself, and shall not resolve the last component of the argument. If the old<\/i> argument and the new<\/i> argument resolve to either the same existing directory entry or different directory entries for the same existing file, rename<\/i>() shall return successfully and perform no other action.<\/p>\n If the old<\/i> argument points to the pathname of a file that is not a directory, the new<\/i> argument shall not point to the pathname of a directory. If the link named by the new<\/i> argument exists, it shall be removed and old<\/i> renamed to new<\/i>. In this case, a link named new<\/i> shall remain visible to other threads throughout the renaming operation and refer either to the file referred to by new<\/i> or old<\/i> before the operation began. Write access permission is required for both the directory containing old<\/i> and the directory containing new<\/i>.<\/p>\n If the old<\/i> argument points to the pathname of a directory, the new<\/i> argument shall not point to the pathname of a file that is not a directory. If the directory named by the new<\/i> argument exists, it shall be removed and old<\/i> renamed to new<\/i>. In this case, a link named new<\/i> shall exist throughout the renaming operation and shall refer either to the directory referred to by new<\/i> or old<\/i> before the operation began. If new<\/i> names an existing directory, it shall be required to be an empty directory.<\/p>\n If either pathname<\/i> argument refers to a path whose final component is either dot or dot-dot, rename<\/i>() shall fail.<\/p>\n If the old<\/i> argument points to a pathname of a symbolic link, the symbolic link shall be renamed. If the new<\/i> argument points to a pathname of a symbolic link, the symbolic link shall be removed.<\/p>\n The old<\/i> pathname shall not name an ancestor directory of the new<\/i> pathname. Write access permission is required for the directory containing old<\/i> and the directory containing new<\/i>. If the old<\/i> argument points to the pathname of a directory, write access permission may be required for the directory named by old<\/i>, and, if it exists, the directory named by new<\/i>.<\/p>\n If the link named by the new<\/i> argument exists and the file\u2019s link count becomes 0 when it is removed and no process has the file open, the space occupied by the file shall be freed and the file shall no longer be accessible. If one or more processes have the file open when the last link is removed, the link shall be removed before rename<\/i>() returns, but the removal of the file contents shall be postponed until all references to the file are closed.<\/p>\n Upon successful completion, rename<\/i>() shall mark for update the last data modification and last file status change timestamps of the parent directory of each file.<\/p>\n If the rename<\/i>() function fails for any reason other than [EIO]<\/b>, any file named by new<\/i> shall be unaffected.<\/p>\n The renameat<\/i>() function shall be equivalent to the rename<\/i>() function except in the case where either old<\/i> or new<\/i> specifies a relative path. If old<\/i> is a relative path, the file to be renamed is located relative to the directory associated with the file descriptor oldfd<\/i> instead of the current working directory. If new<\/i> is a relative path, the same happens only relative to the directory associated with newfd<\/i>. If the access mode of the open file description associated with the file descriptor is not O_SEARCH, the function shall check whether directory searches are permitted using the current permissions of the directory underlying the file descriptor. If the access mode is O_SEARCH, the function shall not perform the check.<\/p>\n If renameat<\/i>() is passed the special value AT_FDCWD in the oldfd<\/i> or newfd<\/i> parameter, the current working directory shall be used in the determination of the file for the respective path<\/i> parameter.<\/p>\n Upon successful completion, the rename<\/i>() function shall return 0. Otherwise, it shall return \u22121, errno<\/i> shall be set to indicate the error, and neither the file named by old<\/i> nor the file named by new<\/i> shall be changed or created.<\/p>\n Upon successful completion, the renameat<\/i>() function shall return 0. Otherwise, it shall return \u22121 and set errno<\/i> to indicate the error.<\/p>\n The rename<\/i>() and renameat<\/i>() functions shall fail if:<\/p>\n
NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
RETURN VALUE<\/a>
ERRORS<\/a>
EXAMPLES<\/a>
APPLICATION USAGE<\/a>
RATIONALE<\/a>
FUTURE DIRECTIONS<\/a>
SEE ALSO<\/a>
COPYRIGHT<\/a> <\/p>\n
\nPROLOG <\/a> <\/h2>\n
NAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
const char *new<\/i>);<\/p>\nDESCRIPTION <\/a> <\/h2>\n
RETURN VALUE <\/a> <\/h2>\n
ERRORS <\/a> <\/h2>\n