内容简介
#include <stdio.h>int rename(const char *oldpath, const char *newpath)
描述
rename()%uA0重命名文件，如果需要在目录之间移动它。Any other hard links to the file (as created using%uA0link(2)) are unaffected.
If%uA0newpath%uA0already exists it will be atomically replaced (subject to a few conditions see ERRORS below), so that there is no yiibai at which another process attempting to accessnewpath%uA0will find it missing.
If%uA0newpath%uA0exists but the operation fails for some reason%uA0rename() guarantees to leave an instance of%uA0newpath%uA0in place.
However, when overwriting there will probably be a window in which both%uA0oldpath%uA0andnewpath%uA0refer to the file being renamed.
If%uA0oldpath%uA0refers to a symbolic link the link is renamed if%uA0newpath%uA0refers to a symbolic link the link will be overwritten.
返回值
On success, zero is returned. On error, -1 is returned, and%uA0errno%uA0is set appropriately.错误
| 标签 | 描述 |
|---|---|
| EACCES | Write permission is denied for the directory containing%uA0oldpath%uA0ornewpath, or, search permission is denied for one of the directories in the path prefix of%uA0oldpath%uA0or%uA0newpath, or%uA0oldpath%uA0is a directory and does not allow write permission (needed to update the%uA0..%uA0entry). (See also%uA0path_resolution(2).) |
| EBUSY | The rename fails because%uA0oldpath%uA0or%uA0newpath%uA0is 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 yiibai), 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.) |
| EFAULT | oldpath%uA0or%uA0newpath%uA0yiibais outside your accessible address space. |
| EINVAL | 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. |
| EISDIR | newpath%uA0is an existing directory, but%uA0oldpath%uA0is not a directory. |
| ELOOP | Too many symbolic links were encountered in resolving%uA0oldpathor%uA0newpath. |
| EMLINK | oldpath%uA0already has the maximum number of links to it, or it was a directory and the directory containing%uA0newpath%uA0has the maximum number of links. |
| ENAMETOOLONG | |
| %uA0 | oldpath%uA0or%uA0newpath%uA0was too long. |
| ENOENT | A directory component in%uA0oldpath or newpath%uA0does not exist or is a dangling symbolic link. |
| ENOMEM | Insufficient kernel memory was available. |
| ENOSPC | The device containing the file has no room for the new directory entry. |
| ENOTDIR | |
| %uA0 | A component used as a directory in%uA0oldpath%uA0or%uA0newpath%uA0is not, in fact, a directory. Or,%uA0oldpath%uA0is a directory, and%uA0newpath%uA0exists but is not a directory. |
| ENOTEMPTY%uA0or%uA0EEXIST | |
| %uA0 | newpath%uA0is a non-empty directory, i.e., contains entries other than "." and "..". |
| EPERM%uA0or%uA0EACCES | |
| %uA0 | The directory containing%uA0oldpath%uA0has 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 theCAP_FOWNERꃊpability) or%uA0newpath%uA0is 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%uA0CAP_FOWNERꃊpability) or the filesystem containing%uA0pathname%uA0does not support renaming of the type requested. |
| EROFS | The file is on a read-only filesystem. |
| EXDEV | oldpath%uA0and%uA0newpath%uA0are not on the same mounted filesystem. (Linux permits a filesystem to be mounted at multiple yiibais, butrename(2) does not work across different mount yiibais, even if the same filesystem is mounted on both.) |