|MKDIR(2)||System Calls Manual||MKDIR(2)|
— make a directory file
Standard C Library (libc, -lc)
char *path, mode_t
fd, const char
The directory path is created with the access permissions specified by mode and restricted by the umask(2) of the calling process.
The directory's owner ID is set to the process's effective user ID. The directory's group ID is set to that of the parent directory in which it is created.
system call is equivalent to
except in the case where path specifies a relative
path. In this case the newly created directory is created relative to the
directory associated with the file descriptor fd
instead of the current working directory. If
mkdirat() is passed the special value
AT_FDCWD in the fd parameter,
the current working directory is used and the behavior is identical to a
mkdir() function returns the
value 0 if successful; otherwise the value -1 is returned and
the global variable errno is set to indicate the
mkdir() system call will fail and no
directory will be created if:
- A component of the path prefix is not a directory.
- A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
- A component of the path prefix does not exist.
- Search permission is denied for a component of the path prefix, or write permission is denied on the parent directory of the directory to be created.
- Too many symbolic links were encountered in translating the pathname.
- The parent directory of the directory to be created has its immutable flag set, see the chflags(2) manual page for more information.
- The named directory would reside on a read-only file system.
- The new directory cannot be created because the parent directory contains too many subdirectories.
- The named file exists.
- The new directory cannot be created because there is no space left on the file system that will contain the directory.
- There are no free inodes on the file system on which the directory is being created.
- The new directory cannot be created because the user's quota of disk blocks on the file system that will contain the directory has been exhausted.
- The user's quota of inodes on the file system on which the directory is being created has been exhausted.
- An I/O error occurred while making the directory entry or allocating the inode.
- An I/O error occurred while reading from or writing to the file system.
- Corrupted data was detected while reading from the file system.
- The path argument points outside the process's allocated address space.
In addition to the errors returned by the
mkdir() system call is expected to
conform to IEEE Std 1003.1-1990
system call follows The Open Group Extended API Set 2 specification.
mkdirat() system call appeared in
FreeBSD 8.0. The
system call appeared in Version 1 AT&T
|March 30, 2020||Debian|