内容简介
#include <sys/stat.h> #include <sys/types.h> int mkdir(const char *pathname, mode_t mode) |
描述
mkdir()%uA0试图创建一个名为路径名的目录。%uA0pathname.The parameter%uA0mode%uA0specifies the permissions to use. It is modified by the process’sumask%uA0in the usual way: the permissions of the created directory are (mode%uA0& ~umask%uA0& 0777). Other mode bits of the created directory depend on the operating system. For Linux, see below.
The newly created directory will be owned by the effective user ID of the process. If the directory containing the file has the set-group-ID bit set, or if the filesystem is mounted with BSD group semantics, the new directory will inherit the group ownership from its parent otherwise it will be owned by the effective group ID of the process.
If the parent directory has the set-group-ID bit set then so will the newly created directory.
%uA0
返回值
mkdir() returns zero on success, or -1 if an error occurred (in which case,%uA0errno%uA0is set appropriately).错误
| 标签 | 描述 |
|---|---|
| EACCES | The parent directory does not allow write permission to the process, or one of the directories in%uA0pathname%uA0did not allow search permission. (See also%uA0path_resolution(2).) |
| EEXIST | pathname%uA0already exists (not necessarily as a directory). This includes the case where%uA0pathname%uA0is a symbolic link, dangling or not. |
| EFAULT | pathname%uA0points outside your accessible address space. |
| ELOOP | Too many symbolic links were encountered in resolvingpathname. |
| ENAMETOOLONG | |
| %uA0 | pathname%uA0was too long. |
| ENOENT | A directory component in%uA0pathname%uA0does not exist or is a dangling symbolic link. |
| ENOMEM | Insufficient kernel memory was available. |
| ENOSPC | The device containing%uA0pathname%uA0has no room for the new directory. |
| ENOSPC | The new directory cannot be created because the user’s disk quota is exhausted. |
| ENOTDIR | |
| %uA0 | A component used as a directory in%uA0pathname%uA0is not, in fact, a directory. |
| EPERM | The filesystem containing%uA0pathname%uA0does not support the creation of directories. |
| EROFS | pathname%uA0refers to a file on a read-only filesystem. |
遵循于
SVr4, BSD, POSIX.1-2001.注意
Under Linux apart from the permission bits, only the S_ISVTX mode bit is honored. That is, under Linux the created directory actually gets mode (mode%uA0& ~umask%uA0& 01777). See also%uA0stat(2).There are many infelicities in the protocol underlying NFS. Some of these affect%uA0mkdir().