Manpage of MKDIR
MKDIRSection: Linux Programmer's Manual (2)
NAMEmkdir, mkdirat - create a directory
#include <sys/stat.h>#include <sys/types.h>int mkdir(const char *pathname, mode_t mode);#include <fcntl.h> /* Definition of AT_* constants */ #include <sys/stat.h>int mkdirat(int dirfd, const char *pathname, mode_t mode);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
- Since glibc 2.10:
- _POSIX_C_SOURCE >= 200809L
- Before glibc 2.10:
DESCRIPTIONmkdir() attempts to create a directory named pathname.
The argument modespecifies the mode for the new directory (see stat(2)). It is modified by the process's umaskin the usual way: in the absence of a default ACL, the mode of the created directory is (mode & ~umask & 0777). Whether other modebits are honored for the created directory depends on the operating system. For Linux, see NOTES 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 (mount -o bsdgroupsor, synonymously mount -o grpid), the new directory will inherit the group ownership from its parent; otherwise it will be owned by the effective group ID of the process.
mkdirat()The mkdirat() system call operates in exactly the same way as mkdir(), except for the differences described here.
If the pathname given in pathnameis relative, then it is interpreted relative to the directory referred to by the file descriptor dirfd(rather than relative to the current working directory of the calling process, as is done by mkdir() for a relative pathname).
If pathnameis relative and dirfdis the special value AT_FDCWD, then pathnameis interpreted relative to the current working directory of the calling process (like mkdir()).
If pathnameis absolute, then dirfdis ignored.
See openat(2) for an explanation of the need for mkdirat().
RETURN VALUEmkdir() and mkdirat() return zero on success, or -1 if an error occurred (in which case, errnois set appropriately).
- The parent directory does not allow write permission to the process, or one of the directories in pathnamedid not allow search permission. (See also path_resolution(7).)
- The user's quota of disk blocks or inodes on the filesystem has been exhausted.
- pathnamealready exists (not necessarily as a directory). This includes the case where pathnameis a symbolic link, dangling or not.
- pathname points outside your accessible address space.
- Too many symbolic links were encountered in resolving pathname.
- The number of links to the parent directory would exceed LINK_MAX.
- pathname was too long.
- A directory component in pathnamedoes not exist or is a dangling symbolic link.
- Insufficient kernel memory was available.
- The device containing pathnamehas no room for the new directory.
- The new directory cannot be created because the user's disk quota is exhausted.
- A component used as a directory in pathnameis not, in fact, a directory.
- The filesystem containing pathnamedoes not support the creation of directories.
- pathnamerefers to a file on a read-only filesystem.
The following additional errors can occur for mkdirat():
- dirfdis not a valid file descriptor.
- pathnameis relative and dirfdis a file descriptor referring to a file other than a directory.
VERSIONSmkdirat() was added to Linux in kernel 2.6.16; library support was added to glibc in version 2.4.
CONFORMING TOmkdir(): SVr4, BSD, POSIX.1-2001, POSIX.1-2008.
NOTESUnder Linux, apart from the permission bits, the S_ISVTXmodebit is also honored.
Glibc notesOn older kernels where mkdirat() is unavailable, the glibc wrapper function falls back to the use of mkdir(). When pathnameis a relative pathname, glibc constructs a pathname based on the symbolic link in /proc/self/fdthat corresponds to the dirfdargument.
SEE ALSOmkdir(1), chmod(2), chown(2), mknod(2), mount(2), rmdir(2), stat(2), umask(2), unlink(2), acl(5) path_resolution(7)
This document was created by man2html, using the manual pages.
Time: 22:27:41 GMT, June 20, 2016